FIND Button

[Paul Hamel via AccessMonster.com]

I wanted to create a Find Record command button on my form. I used the
wizard to create the button (chose the Binocular Graphic), but when i go to
execute the button, I get an error message "Error Accessing File. Network
connection may have been lost".

Am i doing something wrong? How do i set up a control button on my form to
show the "Find Record Field" once we click the button? I would prefer It
finds the record of a person's "Last Name" using "Start of the word" search.

Thanks

 

[Jeff Conrad]

"Paul Hamel wrote in message

I wanted to create a Find Record command button on my form. I used the
wizard to create the button (chose the Binocular Graphic), but when i go to
execute the button, I get an error message "Error Accessing File. Network
connection may have been lost".

Am i doing something wrong? How do i set up a control button on my form to
show the "Find Record Field" once we click the button? I would prefer It
finds the record of a person's "Last Name" using "Start of the word" search.

Hi,

Are you using Access 2000 without SP3 installed by
chance? Is so read on.

I think you've been stung by a particularly nasty bug in
Access 2000. Sure sign is that dreaded "Network Connection
may have been lost.." messsage. Details about it can be
found here:

http://support.microsoft.com/?id=304548

The corruption in your database may not be recoverable.
You might try importing everything into another database.
I believe this bug is fixed with Service Pack 3, but it
will not *fix* corruption already present. To avoid this
bug you absolutely, positively, have to compile your
database EVERY time you import something.

Also, (from Dirk "Yoda" Goldgar) one other thing you might
try first is decompiling your database -- or rather, a
copy of it. Instructions for how to do this may be found
here:

http://www.mvps.org/access/bugs/bugs0008.htm

and here:

http://www.granite.ab.ca/access/decompile.htm

This was also posted by someone from Microsoft (my next employer):

326605 ACC2000: Issues Fixed in Access 2000 by Office 2000 Service Pack 3
http://support.microsoft.com/?id=326605

304548 ACC2000: Error Message: Error Accessing File. Network Connection May
http://support.microsoft.com/?id=304548

After applying Office 2000 sp3 you are going to need to salvage your
database modules (Standard, Forms/Reports) by saving them out to text
files. Example:

- Open Form/Report in design view and select menu option View > Code
- Select the menu option Edit > Select All (to select vba code)
- Select menu option Edit > Copy
- Paste in Notepad file
- Close VBA window to return to Form/Report
- Within the properties Window of Form/Report change the property "Has
Module" from "Yes" to "No"
(this will delete the code behind the object)
- Save your Form/Report
**Repeat above steps for each Form/Report that has code**
- For your Standard module just open and copy to text files

- Then import all your objects (within exception of your Modules) to a new
database file
- Copy the code from the above text files into new modules in your new
database
- For the Forms/Reports reverse the steps by opening their VBA modules and
pasting the code from the text files

*******************************
You can also try running decompile switch but the above methods are
normally your only shot..


I hope this helps! If you have additional questions on this topic, please
respond back to this posting.


Regards,

Eric Butts
Microsoft Access
Good luck,

 

[Paul Hamel via AccessMonster.com]

I'm using Vbe6.dll version 6.4.99.69 and Access 2000. It seems like it is
not the same file version that causes the problem in the info you gave me.
Do you still think it has something to do with a bug in my access?

Thanks

 

[Jeff Conrad]

"Paul Hamel wrote in message

I'm using Vbe6.dll version 6.4.99.69 and Access 2000. It seems like it is
not the same file version that causes the problem in the info you gave me.
Do you still think it has something to do with a bug in my access?

Yep, pretty darn sure.
Access 2000 was particularly buggy out of the box. With the addition
of all three service packs, it is a LOT more stable than it used to be.

If these three conditions all apply, then for sure you have been bitten:
1. Running Access 2000 without service pack 3
2. Running the database on a local drive that does not access anything
on a network (like a linked table to a network database)
3. You have recently imported a code-bearing object (form, report,
or module) and you did not immediately compile the database before
closing it.