The Microsoft Office Access database engine cannot open or write to the file

[June7]

What changed in February - new network server, new computer, new software?



Follow instructions at bottom of my post. Zip the db and other files.

[fongmac]

Yes, they received a new server.

[June7]

Did IT change the name of server? Your code uses S: drive path. Did the pathing get messed up when files were transferred to new server? Can your Windows Explorer navigate to the file location? Is the path still the same structure?

[fongmac]

Yes, the name of the server changed. Would the drive letter matter? I copied the access db file to my desktop to run it and get the same error.

[June7]

Any user running this procedure would need S: drive mapped on their computer. Do you already have an S: drive mapped on your computer? Can you navigate to the Excel file location with Windows Explorer? Can you navigate anywhere on the S: drive mapping? If not, you need to remap the S: drive. Also, if the path structure has changed, need to modify code to reflect that.

Drive mapping can be different on each computer which is why I use UNC (universal naming convention) pathing in code for multi-user db on network server. Of course, even that would not handle changing server name. Code would still need to be modified. Review http://msdn.microsoft.com/en-us/libr...ng_conventions

[fongmac]

I mapped the S drive. Still getting same error.

[June7]

I should have asked - Is this a split database? If it is, I presume not having issue with table links. The frontend is still reading data from the backend tables?

Did IT change permissions for folders?

Try this: put copy of the files (db front and back ends and the txt and spreadsheets) in a folder on your computer at C: root. Change code in this db copy to refer to the files at C: root. Change table links.

If procedure works then I would say IT has done something and you will have to coordinate with them.

[fongmac]

I'm not sure if its a split db. How can I tell? It's only one access file.

[June7]

Look at the tables in the db. If there is a little arrow on the left pointing right then it is a linked table and at least some of the tables are in another file.

A split design is routine when data must be shared. Data would be in file residing on network server. Another file has table links, queries, forms, reports, code. This frontend is usually copied onto user local computer and revisions passed out to users (code can accomplish version updates). Local install allows faster processing.

[athyeh]

Was this issue ever resovled? I am having the exact same issue with a split db...