Re: Access 2000, VBA Code corrupt

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

Hi Michael,

Thanks for responding..

Unfortunately, its only when i open the VBA portion of the form... Access
does not open it up. I still get the "Error accessing file. Network
connection..."... This file is on my local computer...

I've tried to import it into a clean database, and i still get the same
errors.

In the end, i'm just having to re-write the entire thing.

Thanks anyway for the help.


"Michael J. Strickland" <qualityservices2@xxxxxxxxxxx> wrote in message
news:uGqZRAQcJHA.1328@xxxxxxxxxxxxxxxxxxxxxxx
"Rlee" <tech_support@xxxxxxxxxx> wrote in message
news:uQyb0UPcJHA.1184@xxxxxxxxxxxxxxxxxxxxxxx
Hi there,

I am working with Access 2000 and have 2 VBA items that i'm unable to
open.

I am unable to open the VBA Class Code ("Items"), which was originally an
import from a VB6 program.. I had no problem until the other day when i
noticed some odd things happening with the program.

Also, the form that accesses this Items class is also corrupt (the VBA
part, i can see the form itself).

Does anyone know of a way to recover the VBA code itself? I've tried to
do the compact and repair, as well as make sure i am running sp3 and the
vba code is still inaccessable.

The Error i get whenever i open that (or any form) is "Error Accessing
File. Network connection may have been lost".

Thanks to anyone who may be able to help.







If by "unable to open" you mean Access hangs when you try to open it in
Design View, you might try this:

1. Make a backup of the database (in Windows).
2. Open the database and do a compact/repair.
3. Close the database.

4. Re-open the database and import a different, working form (e.g.
frmABC).
5. Run the working form and Hit Ctl-Break to break its code execution.
6. Click on the "Debug" button.
7. Hit Ctl-R to go into Project Explorer.
8. Click on the Reset button to stop code execution.
9. In the panel on the left, select the corrupt form to view its code.
10. Click Debug->Compile to re-compile the corrupter form.
11. Exit design mode saving the form and the database.
12. Re-open the database and your form should be restored.

It seems that sometimes Access (2003 & 2007) forms get corrupt and lose
something which is needed for Design Mode/Compilation. Importing a good
form restores/restarts this process and allows you to open/edit and
restore a corrupt form.


--
-----------------------------------------------------------------------
Michael J. Strickland
Quality Services qualityservices2@xxxxxxxxxxx
703-560-7380
-----------------------------------------------------------------------




.

Relevant Pages

  • Re: Fastest way to do this?
    ... was to install a 'local user-interface' of the database on each PC ... VBA as my front-end though so this isn't really related to my speed ... You can use network monitor to see that Windows goes ...
    (comp.databases.ms-access)
  • Re: Merging content from access
    ... My hunch at the moment is that this is a problem in my access query. ... I agree with you that Word VBA is a more elegent solution. ... The other field-based technique requires you to have a "parent" table as ... the mail merge data source and a child table inserted using a DATABASE ...
    (microsoft.public.word.docmanagement)
  • Re: Possible Project Bug: All Projects in Database are Deleted upon Save
    ... best practices and Project VBA ... > Only Project1 is saved into the database. ... >> prompts with Append or overwrite message. ... >> For Microsoft Project companion projects, ...
    (microsoft.public.project.vba)
  • Re: What happens when data in control is updated
    ... When I developed my concept database file I tended to look at what ... changes expected appearing on the form itself) and not going through the VBA ... > if the primary key field is Text data type, rather than numeric, the ... >>> make sure that a requery is necessary to achieve whatever your aim is. ...
    (microsoft.public.access.formscoding)
  • Re: Moving to SharePoint - Advice?
    ... if you split your database then the front end cannot call those stored procedures. ... However the back end table triggers can of course can call those store procedures that exist in the back end. ... So if your database is un-split, then VBA, or Macro code etc. can call store procedures and values can be returned back. ... just front end tables that are synchonrized periodically with SharePoint, ...
    (comp.databases.ms-access)