Code Window - Appears on start-up

CarolW

Registered User.
Local time
Today, 11:21
Joined
Mar 24, 2006
Messages
58
Good Afternoon,
Could some kind person please point me in the right direction as to how to
stop the 'VB code' window appearing and remaining on my task bar when I initially open up my DB. When I look at whats in the window there seems nothing untoward, but I would simply like to get rid of it as it is annoying??
Other sample db's that I open up on a regular basis are fine, so I was just wondering what could be causing it and how I could avoid it re-appearing..

Hope you can help....


Kind Regards

CarolW
 
Do you have an AutoExec macro? Does it happen when you open with a <SHIFT> key held down?
 
RuralGuy said:
Do you have an AutoExec macro? Does it happen when you open with a <SHIFT> key held down?

RuralGuy,
Thanks for such a quick reply - very much appreciated. I am using an Autoexec macro....??
When I use the <SHIFT> key there isn't a problem and this annoying window is not present. Do you think it could be this AutoExec macro that could be to blame. I would really appreciate any further advice on this matter as I want to get rid of it, so as to not tempt any of my future users to mess around with any of the code that is contained within...

Regards & Thanks


CarolW
 
From the DataBase window look in the Macros section for one named AutoExec. If there is one there then rename it to something else. Do you have a StartUp form? Does your system compile? <ALT> F11 and then Debug>Compile.
 
Code Window - Still Having Problems

RuralGuy said:
From the DataBase window look in the Macros section for one named AutoExec. If there is one there then rename it to something else. Do you have a StartUp form? Does your system compile? <ALT> F11 and then Debug>Compile.

Hi RuralGuy,
As you rightly guessed it, I do indeed have an AutoExec macro and have tried to rename it to something else?? However, if I rename it to something other than autoexec then it refuses to act automatically and in the manner that it was originally intended for! The code window problem goes away but then i've lost the functionality of my AutoExec macro.

I followed further your instructions and believe my system compiles OK - well at least it came back with no errors or other such nasties..

I don't know if it will help but Ive enclosed a print out of the AutoExec Macro Properties/Actions - don't know if it is something wrong that i've done in this area? Ha! Ha!


Your timely response and help is both welcome and re-assuring, especially to a relative new-comer to all things 'Access' and DB orientated.

Thanks again

Best Regards


CarolW
 

Attachments

I'll have to be honest and say I don't use macros. Is your Splash form opening your SwitchBoard form? If so then why not just set the Splash form as the Display Form/Page: on Tools>Startup... Then you would not need the AutoExec macro. Something in your macro is leaving you in a Class module and only you can troubleshoot it unless you want to post your db. You can strip out any sensitive data and compact and then zip it up if you want.
 
Code Window - Problem Still Persisting

RuralGuy said:
I'll have to be honest and say I don't use macros. Is your Splash form opening your SwitchBoard form? If so then why not just set the Splash form as the Display Form/Page: on Tools>Startup... Then you would not need the AutoExec macro. Something in your macro is leaving you in a Class module and only you can troubleshoot it unless you want to post your db. You can strip out any sensitive data and compact and then zip it up if you want.


Thanks RuralGuy,
I'll try what you have just suggested and hopefully that will sort it out??
Failing that I will post it onto you at the earliest opportunity.

Once again many thanks for your help, time and assistance on this matter.


Regards

CarolW
 
in startup you can specify a form to open, and hide the DBS window. if you are doing that and you are being put into a code window, there is something wrong. you should see the problem highlighted in yellow in the code window, because thats the error.

try to compile the dbs - tht will find any syntax errors (though not necessarily logic errors, unfortunately)
 
This happened to me when I deleloped in different versions, ie: developed in A2002 but tested in A2000

I found it was caused by calling functions that are available in the later version but not in the eirlier version. Didn't raise an error, just showed the VB window. Not on the module that was giving the error either.

My suggestion is to look at the autoexec macro and step through each line of code. Comment out lines until the error goes away.

HTH

Dave
 
Code Window - Problem Resolved (I think)

Oldsoftboss said:
This happened to me when I deleloped in different versions, ie: developed in A2002 but tested in A2000

I found it was caused by calling functions that are available in the later version but not in the eirlier version. Didn't raise an error, just showed the VB window. Not on the module that was giving the error either.

My suggestion is to look at the autoexec macro and step through each line of code. Comment out lines until the error goes away.

HTH

Dave

Thanks Oldsoftboss,
I managed to resolve the problem, much to my surprise, by re-naming the modules by adding a 1(or some other figure/text) to the end of each respective one. When I started up my DB the problem with the code window had miraculously gone away - could that have something to do with what you said earlier on about ' calling functions '....

Could re-naming my modules impact on my DB at a later time/date? At present everything seems to be just fine and I am overjoyed at 'resolving' my earlier issue.

P.S
Thanks gemma-the-husky for your earlier response.

Have A Pleasant Weekend


Regards

Carol
 
Renaming the modules will have *no* impact on your db in the future.
 
Code Window - Problem Resolution (Big Thanks)

RuralGuy said:
Renaming the modules will have *no* impact on your db in the future.

Thanks for all of your previous help RG....

I have learned so much from these forums in such a small amount of time!
The excellent advice I have received, on all occasions, coupled with the members patience for new comers like myself is gratefully acknowledged
and well aprreciated.


Keep up the good work ....Hopefully in the not too distant future I will be able to build-up my level of knowledge so that I can impart good advice to those that might need it?


Regards

Carol
 

Users who are viewing this thread

Back
Top Bottom