X   Site Message
(Message will auto close in 2 seconds)

Welcome to UtterAccess! Please ( Login   or   Register )

Custom Search
> Ms Acess Fe - Mysql Be Connection With Runtime    
post Oct 30 2019, 09:04 PM

Posts: 14
Joined: 15-April 08

For the first time, I have successfully split an access d/b with the BE located on a MySQL remote server (accessed via an IP address). The FE (on my machine) is connected using the MySQL ODBC 8.0 Unicode Driver and works well with the remote BE.

My challenge is getting it to work with MS Access Runtime on another (single) PC in different location. Is there a way to accomplish this? My understanding is that the compiled MS Access file (*.accde) is somewhat self-contained to work with Runtime and has the connection information to point to the remote d/b. I've attempted to make it work, but to no success. iconfused.gif Can a compiled FE work on its own with Runtime or is there more that has to be done? Do I have to create a DSN-less connection with VBA?

Thanks in advance for any help.

Go to the top of the page
Start new topic
post Oct 30 2019, 09:50 PM

UtterAccess VIP
Posts: 2,964
Joined: 12-April 07
From: Edmonton, Alberta Canada

Yes, it should work.

However, you need and want to force access to use DSN-less connection.

Thankfully, that is the default, but ONLY if you choose to use a FILE DSN during the linking process.

If you link all your tables, but MAKE sure you created + used a FILE DSN when you did the linking?

Well, then you can compile to the accDE, and running that accDE with the runtime should work on any machine that is part of your network and has use of the same IP address you used on your development machine when linking.

Now, over time a good many people will adopt some kind of re-link code, and that re-link code will also (should be) DSN-less.

However, if you out of the box link all tables using a FILE DSN, then after linking, access does not use nor care about the DSN - it is ignored, and the DSN can even be deleted, or in your case not present on the machines you plan to deploy to.

I should point out that if you link using a "user" or "system" DSN then all of the above does not apply, and access will not by default create DSN-less links.

So the key concept and trick here is to ensure that you linked the tables using a FILE dsn.

Albert D. Kallal (Access MVP 2003-2017)
Edmonton, Alberta Canada
Go to the top of the page

Posts in this topic

Custom Search

RSSSearch   Top   Lo-Fi    28th March 2020 - 04:16 PM