[AccessD] AutoExec Macro Question

Susan Zeller szeller at cce.umn.edu
Thu Mar 6 10:35:01 CST 2003


Yup, it's a public function.

-----Original Message-----
From: Seth Galitzer [mailto:sgsax at ksu.edu] 
Sent: Thursday, March 06, 2003 10:14 AM
To: accessd
Subject: RE: [AccessD] AutoExec Macro Question


Susan,

One more thing to check.  Are you sure basLoad is a function and not a
sub?  IIRC, the RunCode macro directive will only call public functions
and not subs.  Another way to test is to open any module and try to run
the function from the Immediate Window.  Just type
	?basLoad
anywhere in the window.  If it is a function and it is public, it should
run.  If it doesn't run, then chances are one of those two things is not
true.

Seth

On Thu, 2003-03-06 at 09:55, Susan Zeller wrote:
> Chris,
> 
> I know, I know!  I have never used a Macro before, but in this case, 
> my splash screen is also my main menu page and so users return to it 
> over and over.  The code that I wanted to call in the Autoexec Marco 
> creates a connetion to my SQL Server using "Application Role" 
> security.  The way this works, I can only run this code once during 
> the application. If it's called a second time, it gives an error.
> 
> I changed the name of the function from Load to basLoad can put
> basLoad() in the macro.  None of that works.  So, I'm building a 
> separate splash screen and putting the basLoad on open of that form.
> 
> Still seems a mystery to me, though.
> 
> --Susan
> 

-- 
Seth Galitzer			sgsax at ksu.edu
Computing Specialist		http://puma.agron.ksu.edu/~sgsax
Dept. of Plant Pathology
Kansas State University

_______________________________________________
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com



More information about the AccessD mailing list