module error

[piet123]

hi,

i have 2 seperate db's that has no relation to each other.
i have a module in db1 which i want to use in db2.

- i have imported the module from DB1 into DB2.
- in the access window (modules) the module name displays, and in vba window it displays the module name also.

- this is all ok.
- but now: when i click on the module name in vba (to edit the code), then access gives error:

"error accessing file, network connection may have been lost"
or something like that.

both db's are not on network but running from local harddisk.

any help please.

regards,
Piet.

 

[KenHigg]

I would start by stepping through the code with debug to see where it zonks...


kh

 

[WayneRyan]

Piet,

Common problem, many sources:

http://www.access-programmers.co.uk/forums/search.php?searchid=249168

You might try:

Tools --> Database Utilities --> Compact/Repair first.

Wayne

 

[WayneRyan]

Piet,

Ignore last post for the moment. This is probably it exactly:

http://support.microsoft.com/default.aspx?scid=kb;EN-US;304548

Wayne

 

[piet123]

thanks wayne

Piet,

Ignore last post for the moment. This is probably it exactly:

http://support.microsoft.com/default.aspx?scid=kb;EN-US;304548

Wayne

thank you, all fixed up now.

have a good day.
Piet.

 

[supmktg]

I'm working on an mdb built by some one else. I imported a module from a sample db that I found on this forum (which by the way was a great help!), and then ran into this "error accessing file" error. My version of the Vbe6.dll file is not 6.3.91.8 which MS claims is the cause of this problem, but I'm going to update to SP3 anyway. The MS instructions say "You must install this service pack on all computers that run Office 2000". Will others have trouble running mdb's that I work on if they are running less tha SP3?