runtime error 2004

[officemanager2]

I made a big (and dumb) mistake today and have been stuck creating a fix for it.

The computer I use to create the database is running on XP using access 2003. There is another computer in the office used for calling out BUT it runs on on access 2000. I create the forms, add VBA, etc using the 2003 version of access and then update the computer with the 2000 version of access (ideally the whole office would be on the same network, but we're small and can't afford the upgrades at this point).

So today for some bizarre reason I over wrote the 2003 version of the database with the 2000 version and now constantly get the run time error 2004.

I looked into this and have tried everything from altering the RAM down to 512 (didn't work) to using the database utilities/convert database from the 2000 access version to the 2003 access version and still no luck.

I attempted to recover the overwritten file using software but that was no good either.

The runtime error occurs when I perform searches for specific records in the database. The first search will work, but any search after that will not work and I have to shut the program down and restart to get that one search done.

If anyone has suggestions I'm open.

 

[seaport]

Could you post the error message text for error 2004?

The first thing I would try is to create a blank new Access 2000 database and import all objects from the database with problems.

 

[officemanager2]

I've tried to use print screen but I don't have paint on this computer to post the screen. Not much more to add to the error message, it reads as follows:

Run-time error '2004':

There isn't enough memory to perform this operation. Close unneeded programs and try the operation again.

From research on line and testing the computer the ram is fine, the issue appears to be with the DAO (which I know very little about) in the access program. Since the last post I've tried repairing the program using the install disc and that had no effect, I've also again reduced the ram down to 512 but also no effect.

A very odd problem and one that others have had.

I have also tried to use cut and paste and recreate the database, but the problem remains. I believe because what I'm cutting and pasting from is the 2000 version of the database, but I can't see why this would have such and affect. At this point I'm either going to redo the entire structure of the database, or remake the forms from scratch and import the table data and retype the VBA. I'm still open to suggestions though.

 

[PHV]

Why not simply restarting from your latest backup ?

Hope This Helps, PH.
FAQ219-2884
FAQ181-2886

 

[officemanager2]

Tried that and I still get the error. I don't think there is much more I can do at this point. I don't think the error is in the database, but rather in the registry so I'll pursue that for a while and see if it goes anywhere. From other things I've read this is an issue that is based in the operating system working with the office suite and there is not a fix for it so I think that is where things will end.

 

[seaport]

I remember running into this message before. I cannot recall the exact situation because it was a very rare problem. I am pretty sure it has nothing to do with memory.

You can import several modules and test the database at a time, in order to isolate the problem.

Good luck.

 

[MajP]

I have seen this posted several times, and the problem never seems to deal with Memory. Usually it is
1)Corrupt database
2)Jet version

http://support.microsoft.com/kb/191743/EN-US/

3)possibly max locks per file.

http://support.microsoft.com/default.aspx?scid=kb;en-us;161329

To try to fix this.
1)Ensure you have all windows and office service packs installed!
2)Ensure you have the most current JET version

http://www.microsoft.com/technet/security/bulletin/fq99-030.mspx

3) decompile and then recompile your current db

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

4)Create a new blank database
5)Using import from external data, import in the Tables.
Then import all other objects.
6) Compact and repair the new db

Use the search feature on this site to see if you can find any references to this problem.

 

[officemanager2]

It's an odd one. There is a runaround one can find online that has to do with 'ungrouping' but when I open the forms in design view there is no grouping taking place. The other popular fix on the net is reducing the computer ram to 512 but this had no affect either. I think that unfortunately this is a bug deep in the system. If you know sites where I can get the modules that would be great as I'm moving forward with this but the error remains which means it will probably spread, or manifest itself at an even worse, meaning busier time of year. I'm now getting a script error when I open outlook which wasn't there before, and this started the same time the 2004 error is occurring. Maybe separate as I believe script errors are java but odd both errors began at the same time. Thanks to both of you for the input.

 

[officemanager2]

Thanks MajP I was replying while you posted so I'll try those links.

 

[MajP]

I searched this site and there were a few "2004 error posts". Unfortunately, no one seemed to get a solution.
Out of curiosity could you look for
MSJETXX.dll
in windows/system32 file

Right click on the file and pull of the properties page. Click on the version tab and post the JET version.

 

[officemanager2]

the jet version is

4.00.9511.0

 

[MajP]

What happens when you convert this 2000 version to 2003 format?

 

[officemanager2]

Nothing. It says it has converted but the end result is the same with the run time error 2004.

 

[PHV]

And what about a system restore point ?

Hope This Helps, PH.
FAQ219-2884
FAQ181-2886

 

[MajP]

The other big question is which computer/s does this happen?
The 2003 one?
The 2000 one?
Or both?

 

[jontout]

Is it worth reindexing the database used in the search?
I'd check that during the upgrade all data types have remained as in the previous solution.

 

[officemanager2]

Hi

MajP

The problem is on the 2003 computer. The 2000 computer is working fine.

PHV

Haven't thought about a system restore actually. It seems worth a try but I need to get caught up with some other things before trying that.

jontout

I don't know how to reindex the database?

 

[jontout]

You'd open the main table in design mode, and assuming you have an AutoNumber field as the Primary Key, you would remove the PK from that field, change it to a number - save the table - then add a new AutoNumber field as PK and remove the original field.

I can't think of a tool that does this but it's easy enough if you're used to creating tables in Access.

 

[jontout]

I'd should probably also add, that if I had time I'd be inclined to export the data to Excel check the integrity and import back into freshly created, identical databases...

 

[officemanager2]

Jontout: I'm trying to fit your fix in on Friday. I'll let you know how it goes. thanks