Wrong Path error 3044

Topic

New Reply

I have just updated a small database to Access 2000 for a customer. I’m not certain but I believe it originated in 2.0.

The data is held in a separate table (cleverly named ___data) which happens to be in the same directory.

When he tries to open four of the six forms in the database he gets a 3044 Wrong path error and the message indicates that it is looking for the ___prog database in the directory on my computer. He can edit all of the forms.

I have moved the files to different directories on my own computer and also to my second computer without being able to duplicate the problem.

I created two new blank databases and imported from the old tables but the result was the same both here (no problem) and at the client’s (error 3044).

The client is running Win 2000 while both of my machines are on W98.

Any ideas on where to start?

Reply | Quote

Replies

IF YOU ARE WORKING ON A NETWORK
YOU SHOULD TRY UNIVERSAL PATHING ON THE LINKED TABLES
SERVERNAMEFOLDERSUBFOLDERDATABASE.MDB
INSTEAD OF A DRIVE LETTER
HTH
JerryC

Reply | Quote

I’ll keep the universal path in mind when it ultimately is networked. In the meantime there is no trouble finding the data. Access seems not to be able to find itself

Reply | Quote

I would start by changing the file name and getting rid of those underscores. Cute names like that can cause all kinds of grief, so change it and relink the file. It sounds like Win2K spits up on the odd name.

Reply | Quote

Sorry to have mislead you. The underscores represent the customer’s data name and this guy is unbelievably sensitive. There are 11 letters in each of the names with no spaces or other marks.

Reply | Quote

Are the problem forms in the front end based on queries? If they are have a look at the properties of the queries (in design mode). I once spent time tracking down a strange problem with linking in a database designed by someone else and it turned out the query had a setting for the SourceDatabase. Maybe something similar is happening here.

Reply | Quote

All of the forms are table based. There are two subforms in the main form.

Since my last post I tried importing the program file into a new database on my second computer. All that did was give the customer a different path error.

The customer then tried the database on a W98 machine with the same result. We have worked around the problem by copying into a blank table on his machine. During the import, there was a message about the invalid path (sorry I can’t be more specific but I was just listening to the customer over the phone) but the import continued and the resulting database works.

Pity that’s not the machine that it will have to run on.

Reply | Quote