Microsoft Access problem

[Micko]

Hi, guys
I know this is not the best place to post this problem, but trust me I've searched the net and coundn't sove my problem.
I got Microsoft Access .mde file (without any code) and on my computer everything works fine, but when I copy that database on my friend's computer then start I getting the following error message:

The expression On Current you entered as event property setting produced the following error: A problem occured while Microsoft Access was communicating with the OLE server or ActiveX Control.

Configuration are simmilar:

Mine: AMD 750, 256MBRAM Visual Studio .net, SQL Server. Office XP
Friend's Intel PIII 700 MHz, 128 MB, Visual Studion.net, Office XP, no SQL Server.

I simply don't know what to do I tried everything, but on some machines does work on others don't.
If someone has any advice, it would be very valueable to me.

Pleas don't get angry because of this post, but you're my last hope.

Thank you

[Fordy]

I've come across a few weird moments with access. 3 possible remedies;

1. Open a command window and run "myAccessDB.mdb /decompile". The go back in, Ctrl-F11 (get the VBA window up) and try recompile
2. Export into a fresh DB (drastic)
3. One problem I had once was on a PC with 2 versions of Office that made access choke. Getting rid of the older version and then run the Office XP service patch - available from Microsoft.com

[Fordy]

Also, I'll move this to Tech, as it's not really General Discussions material

[ober]

Install the MDAC driver on the friend's machine... and Jet also, if you're using that to access the file.

[Micko]

Install the MDAC driver on the friend's machine... and Jet also, if you're using that to access the file.

I've downloaded MDAC and Jet (which was very painfull because of my connection 28.8K) but that didn't help. I'm begining to think that database is not made correctly.
And Fordy, when I type database.mde/decompile it just start Acccess and everything is the same when I opened it normally (double click). When press Alt+F11 I see VB forms but they are locked.

Anyway thanks for help.

[Fordy]

Access is a tricky beast when sharing it across workstations: I jsu spent a big part of today trying to get a and Access DB I wrote in work to work on 2 PCs. I know now when I try it on a third that i'll get more grief.

Are you sure that all of the references & object you use on the first pc are available and of the same version on the second?

[andyhunter]

The expression On Current you entered as event property setting produced the following error: A problem occured while Microsoft Access was communicating with the OLE server or ActiveX Control.

Chances are the database is trying to communicate with a COM object not installed on your friends machine. I have experienced this before when transferring an access DB from one network over to another that had an older / not complete install version installed.

There have been many changes to MS Access since its debut and huge changes were made with the release of Access 2000 and then again with the release of Access 2002 (XP). I have found that a lot of Activex components present with 2002 do not exist within Access 2000. The problem is that an mde simply compiles the VBA code, it does not produce a stand alone program.

So the solution would be to try and figure out what Activex control the DB is trying to load and then install that on your friends machine. (Normally they are present in a dll file). Note: you will have to register the dll in order for COM to work properly.

[gvb]

Similar mistake can be in case of problems with different region settings on different PCs.