When in Access every I try and run the VB editor from either an object
properties or ALT F11 the whole program shuts down...Its as if I hit the
close button .

Sounds like a corrupted VBA project to me. You can try opening Access with
the undocumented /decompile switch. If you only have one version of Access
installed, then click on Start > Run and enter:

msaccess /decompile

Then, while holding down the shift key to bypass any startup form (or
autoexec macro), open your database. Try compacting it using Tools > Database
Utilities > Compact and repair database.

If that does not help, then try the following:

Create a brand new database and immediately disable the NameAutocorrupt
feature (see: http://allenbrowne.com/bug-03.html for reasons why you want to
do this). Then import all objects from the suspect database into the new
database, one group at a time. In other words, import all tables (but not
linked tables), then import all queries, then all forms, etc. While Access
will allow you to import all objects in one operation, the experts at FMS,
Inc. (a Microsoft Partner), have stated that it is best to import objects one
group at a time (Reference:
http://www.fmsinc.com/ubb/Forum12/HTML/000285.html).

Recreate any linked tables from scratch. Access can cache a lot of
information about linked tables, which may no longer be valid, so it's always
best to recreate the linked tables from scratch. When importing local tables,
make sure to check the option to import relationships, menus and toolbars,
and import/export specs. If any of the local tables in the source DB are
hidden, you'll need to first unhide them. You will need to set the checked
references to match the source database, along with any startup options set
under Tools > Startup. Going through this process often times solves
corruption problems, because you get a new set of the hidden system tables
(the tables whose names start with "MSYS"). These system tables are updated
appropriately as you import objects.

This may sound like a lot of work, but it really isn't. Creating a new
container DB, disabling NameAutocorrect, importing all objects one group at a
time, re-establishing any linked tables, setting startup options, and setting
references to match the source DB is usually a fairly quick procedure. When
you are in the Visual Basic Editor, in order to check that the references
match the source DB, you should do a Debug > Compile ProjectName as well.


Tom Wickerath
Microsoft Access MVP

http://www.access.qbuilt.com/html/ex...tributors.html
http://www.access.qbuilt.com/html/search.html
__________________________________________


"traderbrown" wrote:

> When in Access every I try and run the VB editor from either an object
> properties or ALT F11 the whole program shuts down...Its as if I hit the
> close button .

Thanks Tom , I will try that.

"Tom Wickerath" wrote:

> Sounds like a corrupted VBA project to me. You can try opening Access with
> the undocumented /decompile switch. If you only have one version of Access
> installed, then click on Start > Run and enter:
>
> msaccess /decompile
>
> Then, while holding down the shift key to bypass any startup form (or
> autoexec macro), open your database. Try compacting it using Tools > Database
> Utilities > Compact and repair database.
>
> If that does not help, then try the following:
>
> Create a brand new database and immediately disable the NameAutocorrupt
> feature (see: http://allenbrowne.com/bug-03.html for reasons why you want to
> do this). Then import all objects from the suspect database into the new
> database, one group at a time. In other words, import all tables (but not
> linked tables), then import all queries, then all forms, etc. While Access
> will allow you to import all objects in one operation, the experts at FMS,
> Inc. (a Microsoft Partner), have stated that it is best to import objects one
> group at a time (Reference:
> http://www.fmsinc.com/ubb/Forum12/HTML/000285.html).
>
> Recreate any linked tables from scratch. Access can cache a lot of
> information about linked tables, which may no longer be valid, so it's always
> best to recreate the linked tables from scratch. When importing local tables,
> make sure to check the option to import relationships, menus and toolbars,
> and import/export specs. If any of the local tables in the source DB are
> hidden, you'll need to first unhide them. You will need to set the checked
> references to match the source database, along with any startup options set
> under Tools > Startup. Going through this process often times solves
> corruption problems, because you get a new set of the hidden system tables
> (the tables whose names start with "MSYS"). These system tables are updated
> appropriately as you import objects.
>
> This may sound like a lot of work, but it really isn't. Creating a new
> container DB, disabling NameAutocorrect, importing all objects one group at a
> time, re-establishing any linked tables, setting startup options, and setting
> references to match the source DB is usually a fairly quick procedure. When
> you are in the Visual Basic Editor, in order to check that the references
> match the source DB, you should do a Debug > Compile ProjectName as well.
>
>
> Tom Wickerath
> Microsoft Access MVP
>
> http://www.access.qbuilt.com/html/ex...tributors.html
> http://www.access.qbuilt.com/html/search.html
> __________________________________________
>
>
> "traderbrown" wrote:
>
> > When in Access every I try and run the VB editor from either an object
> > properties or ALT F11 the whole program shuts down...Its as if I hit the
> > close button .

OK , to define the problem a little further I have found that the Visual
Basic editor will not load at all. weather I'm in Word, Excel or Access when
I press ALT F11 the program shuts down as if I had hit the close button.
However I have tried Tom's suggestion. I have also reinstalled office and
have downloaded SP2.
A full Symantec scan has also been carried out incase a virus issue.

Any further suggestions would really help

"traderbrown" wrote:

> Thanks Tom , I will try that.
>
> "Tom Wickerath" wrote:
>
> > Sounds like a corrupted VBA project to me. You can try opening Access with
> > the undocumented /decompile switch. If you only have one version of Access
> > installed, then click on Start > Run and enter:
> >
> > msaccess /decompile
> >
> > Then, while holding down the shift key to bypass any startup form (or
> > autoexec macro), open your database. Try compacting it using Tools > Database
> > Utilities > Compact and repair database.
> >
> > If that does not help, then try the following:
> >
> > Create a brand new database and immediately disable the NameAutocorrupt
> > feature (see: http://allenbrowne.com/bug-03.html for reasons why you want to
> > do this). Then import all objects from the suspect database into the new
> > database, one group at a time. In other words, import all tables (but not
> > linked tables), then import all queries, then all forms, etc. While Access
> > will allow you to import all objects in one operation, the experts at FMS,
> > Inc. (a Microsoft Partner), have stated that it is best to import objects one
> > group at a time (Reference:
> > http://www.fmsinc.com/ubb/Forum12/HTML/000285.html).
> >
> > Recreate any linked tables from scratch. Access can cache a lot of
> > information about linked tables, which may no longer be valid, so it's always
> > best to recreate the linked tables from scratch. When importing local tables,
> > make sure to check the option to import relationships, menus and toolbars,
> > and import/export specs. If any of the local tables in the source DB are
> > hidden, you'll need to first unhide them. You will need to set the checked
> > references to match the source database, along with any startup options set
> > under Tools > Startup. Going through this process often times solves
> > corruption problems, because you get a new set of the hidden system tables
> > (the tables whose names start with "MSYS"). These system tables are updated
> > appropriately as you import objects.
> >
> > This may sound like a lot of work, but it really isn't. Creating a new
> > container DB, disabling NameAutocorrect, importing all objects one group at a
> > time, re-establishing any linked tables, setting startup options, and setting
> > references to match the source DB is usually a fairly quick procedure. When
> > you are in the Visual Basic Editor, in order to check that the references
> > match the source DB, you should do a Debug > Compile ProjectName as well.
> >
> >
> > Tom Wickerath
> > Microsoft Access MVP
> >
> > http://www.access.qbuilt.com/html/ex...tributors.html
> > http://www.access.qbuilt.com/html/search.html
> > __________________________________________
> >
> >
> > "traderbrown" wrote:
> >
> > > When in Access every I try and run the VB editor from either an object
> > > properties or ALT F11 the whole program shuts down...Its as if I hit the
> > > close button .

This definately does not sound good. I suppose one possibility might be found
in this KB article (likely applies to Access 2002 and 2003 as well):

http://support.microsoft.com/kb/248790

Which version of Office do you have? Your mention of SP-2 leads me to
believe that you may be working with Office 2003...in any case, you may need
to find a KB article that describes how to completely remove Office from your
PC, before attempting to re-install it.


Tom Wickerath
Microsoft Access MVP

http://www.access.qbuilt.com/html/ex...tributors.html
http://www.access.qbuilt.com/html/search.html
__________________________________________

"traderbrown" wrote:

> OK , to define the problem a little further I have found that the Visual
> Basic editor will not load at all. weather I'm in Word, Excel or Access when
> I press ALT F11 the program shuts down as if I had hit the close button.
> However I have tried Tom's suggestion. I have also reinstalled office and
> have downloaded SP2.
> A full Symantec scan has also been carried out incase a virus issue.
>
> Any further suggestions would really help

Thanks Tom , I will try this....to date I have found the KB article on
reistalling and have also reinstalle the VBA6.dll with no luck. I'll let you
know when I find an answer

Cheers


"Tom Wickerath" wrote:

> Some new information for you...
>
> Try using the Windows Installer CleanUp Utility to help remove errant
> registry settings:
> http://support.microsoft.com/?id=290301
>
>
> Then follow the instructions in this KB article to manually delete Microsoft
> Office from your PC:
> http://support.microsoft.com/kb/827428
>
> This article was written for Office XP, but the directions are likely
> similar for Office 2003. See the section titled "Manually remove the program
> folders and the temporary files". The first two steps should be taken care of
> by using the Windows Installer Cleanup utility.
>
> Then try re-installing your version of Office, followed by the service packs
> and the latest version of the JET database engine.
>
>
> Good Luck!
>
> Tom Wickerath
> Microsoft Access MVP
>
> http://www.access.qbuilt.com/html/ex...tributors.html
> http://www.access.qbuilt.com/html/search.html