linking a split database table in Access Runtime

Question

I built a database in MS Access 2010.  The end users are only using MS Access Runtime 2013 so I split the database before I transferred it to the new PCs.  There was no way for me to link the Front End to the back in runtime.  I used some code I got from JStreet Tech, and it works if I am on the computer that has Acess 2010 installed.  However, I get a "compiling error" when I run it on any of the 3 PCs that will be using this db.

Is there a better way to do this or is there a "bullet-proof" code to add to my db?

Thanks,

Answer 1

You did not answer my question re ACCDB or ACCDE.

> Check the code and recompile it

Did you do that? Open a code window, then select Debug > Compile.

Answer 2

Error description:

There was an error compiling this function

The visual basic module contains a system error.

Check the code and recompile it.  OK

The I get a dialog box...

Macro Single Step

Macros Name:  Autoexec

Action Name:  RunCode

Arguments:  jstchecktablelinks_full()

Error Number:  7960

When I close this dialog box, the program closes...

A final box appears that says:

Microsoft Access

Could not use 'Admin'; file already in use.

And then the program closes completely.

I've split other databases before without issues.  However, since I didn't write this code, I'm not sure how to troubleshoot it.  Plus, when I run it on a PC that has Access installed, I don't get the error.

Answer 3

All three are 64bit machines.  Two laptops and a desktop (not that that matters). Two are running Windows 10 and one is Windows 7.  All three have the same issue.

This is a very simple database and it didn't have any code before I copied in the above mentioned code.  So, it would have to be with the linking. 

I should add, the error comes up as soon as the app opens.  The only option is to close the dialog box which closes the app.

Answer 4

Please quote any error messages VERBATIM.

A compile error would be strange because I'm sure you are distributing an ACCDE front-end file per best practices, not an ACCDB, so there is nothing to compile.

90% chance this is a References problem: you can write code in your startup routine to look for broken references (see IsBroken property of the Reference object).

Answer 5

Are all the PCs running 32 bit versions of Access?

You could always try the old tried and tested mvps.org relinking code, see : http://access.mvps.org/access/tables/tbl0009.htm

Are you sure the compile error is related to the relinking, or could it be something else?