Error accessing file ? (2000/1)

Topic

New Reply

All of a sudden, my macros dont work, at all

I cant run or paste them; the error message when i try to do anything with the functions/subroutines is “Error accessing file. Network connection may have been lost.”

I cant delete the module; same error message.

Help presents a blank screen.

Argh! What to do?

Reply | Quote

Replies

Is the database or its back end on a network drive? And what *is* the back end? If it is an ODBC database, then have you checked the DSN?

Is Access run from an application server, or is it installed locally? Have you tried a detect and repair? Have you tried JetComp? Have you tried a decompile?

I’ve also seen some very strange behavior when I received a file created on a Windows 2000 machine where SQL Server 2000 hadn’t quite managed to get installed. It apparently changed *one* of the ADO libraries to version 2.6 but left the others at 2.5. When I get a copy of the Access front end, I get compile errors every which way and may not even be able to remove the missing reference.

Reply | Quote

For me the scary part is: No front end, no back end, no network! Just a single database on my single machine. Let me mention that i have only been doing database work long enough to get into trouble .

I neglected to mention that i had tried to import most of the tables, queries, forms, and modules from one mdb to another. I am trying to normalize a dbf that is as flat as paint, and after trying one decomposition, i may discard it, and move on to another.

It was right after i imported everything that nothing worked (!?), and it seemed like nothing worked in the previous mdbs any more either, but that was at 130am, so i will regroup and try to think thru this again.

Perhaps the names of the modules has to match the name of the database???

One anomaly: I import the modules, and then use the builder in a query. The builder cannot find any functions in the module, which is why i think there is some kind of a naming problem.

Reply | Quote

Do you have permissions to the database you’re importing from? What version of Access was it built in?

The only restriction on module names is that you can’t have two with the same name. Access doesn’t care what you call them. However, the builder only looks at functions. If your modules contain nothing but sub routines, the builder won’t see them anyhow. Click on the modules tab in the database window, select one of the modules and hit the design button. That will take you to the VB editor and display any code in the module.

In the VBE, go to Tools–>References and see if any of them display a big MISSING in front. If it does, then you need to uncheck that reference and find the equivalent on your machine either from the list or by browsing. When you import objects from another database, it doesn’t bring in the references, so that may be your problem.

Then do a Run–>Compile from the VBE. That will find anything that is bad in the code. If the database was created in Access 97, you probably will need to set a reference to DAO 3.6 because otherwise Access will choke on things like Dim dbs As Database.

Reply | Quote

Yep, i have all permissions. A2K sp1. I am building the mdb from dbf files by normalizing the tables, so there should be no versioning problems at all. I am in complete control

It feels like something got ‘poisoned’ — an mdb opens fine, but when i try to look at various Modules it throws the Error accessing file msg.

I am going to write off that day’s work as a loss, and try to remember what i did. Meanwhile, I will check the Tools–>References

Reply | Quote

I am getting the EXACT same error. I have no idea what happened, either. I’ve tried uninstalling and reinstalling access. It’s affecting multiple databases. Any suggestions?

Reply | Quote

I still dont know what happened, but i was able to open a new mdb and import the tables from the smitten database, and moved on from there. I am attributing it to Phase of Moon.

Reply | Quote