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

This is my second attempt to reply to Albert's last comment.  So, I hope this doesn't duplicate...

Albert,

Thank you for your reply.

The code I used that did not create an error this time is from the link that Tom sent me.  I went back and looked over the code from the JStreet link and wasn't sure: #1 - what part of the code would be in the autoexec macro; and #2 would the code section from JStreet work with the code that from Tom's link.

So, again my question would be:  Using the code from Tom's link, what should I put in an autoexec macro and/or can I put a button on the screen to run the re-link manually.

Thanks to all of you for your continued assistance.

Jim

Answer 2

Good, it seems you finally started to follow the steps outlined.

As I noted, you needed to try and compile your original system.

Now that we cleared up that your original application  compiles, then the next step I suggested was to import the code and try compiling again. And it seems that you also finally followed that advice, and that suggestion now works.

Now that you done the above two steps, then next is to have the re-link code run on start-up (that advice of mine you seems to ignored).

The two suggestions I outlined you can use are:

#1 – have your start up form and code run the re-link code

#2 – import the Auto Exec macro from the re-link sample.

Likely just best to adopt and follow the above suggestion #2.

If you import the autoexec macro from that sample j-street example, then the re-link code will always automatic run for you on application start up. You should not need to do anything additional.

So once you done the above, then you should compile the application to an accDE and that is the front end part you distribute (place) and test on the runtime computer.

Regards,

Albert D. Kallal (Access MVP)

Edmonton, Alberta Canada

Answer 3

Tom,

Thank you.  I copied the code into the application and copied the front end to the laptop that has the runtime version on it.  Good news first, no errors appeared!  Yeah!

However, was something suppose to launch to link the front end to the back or can I make a "button" to launch the code?  If the button, what action and parameters am I to use?

I think this is getting closer.

Thanks,

JT

Answer 4

Check this out: http://access.mvps.org/Access/api/api0001.htm

It sounds like you have a mismatch of code from several places, and not all the pieces are in place.

Answer 5

Well, no need to have created a module. You can usually just hit ctrl-g and that jumps you to the VBA editor. At that point you just do a debug->compile.

What this means is that BEFORE you done any changes, and BEFORE you trying to use the j-street linking code, your database seems to have code modules missing.

At this point then, your issue and question has nothing to do with the re-link code. You want to “fix” up the application and find these general errors and issues BEFORE you attempt importing the re-link code. Do this before you introduce ANY new code.

So I would not worry about the re-link code until such time you fix and create a proper working application. It makes “little” sense to introduce new code and modules when the existing application has code errors.

In fact, I would go back to the original un-split database and find + fix the compile errors. So does the original un-split database not compile? (Does it have code parts missing?).

So spend all your time on the un-split database. Get rid of all compile errors.

What this suggests is that your original database/application you working on has issues and problems – and those issues and problems need to be fixed LONG before you attempt to introduce additional code and modules.

>> There is no code in the original

If there is no code in the original then where is the code you posted coming from such as fGetMDBName?

So what you given so far is confusing.

If there is no code in the original database, then how is the debug->compile failing? Cleary “some” code must exist else no compile errors would exist when no code exists.

Regards,

Albert D. Kallal (Access MVP)

Edmonton, Alberta Canada