We have a couple of different profiles in the office. Everytime the users switch from one to the other, they have to start the APPLOAD command, then close the dialog (doing nothing in the dialog mind you) to get our VBA apps to run.
Any ideas?
|
We have a couple of different profiles in the office. Everytime the users switch from one to the other, they have to start the APPLOAD command, then close the dialog (doing nothing in the dialog mind you) to get our VBA apps to run.
Any ideas?
If you are still having trouble with this...
Check your profile paths are they identical? It sounds like your application is dependant upon the support file search paths in your profile.
They are. Does that mean that the Startup Suite is initiated before the support paths are loaded?
I could simply add the support path to the other profile, but I don't want the programming available.