Problem with accdb association on user's desktops

[burma]

if you have the "latest" version of Office, don't mix it with older version.
if you need to develop on lower version, install it on a Virtual Machine.
Oracle offers VirtualBox, a free Virtual machine,

I agree but until users I'm supporting uninstall the older version, I have to support them with what they have.

 

[theDBguy]

I agree, but until the users I'm supporting uninstall the older version, I have to support them with what they have.

I have no experience with this but take a look. Maybe it's something you can use?

Microsoft Access Version and Database Launcher: Total Access Startup ensures the right version is always started

Total Access Startup ensures the correct version of Access and your database are launched and installed properly. Easily deploy Access databases across a network and centrally manage them.

www.fmsinc.com

 

[arnelgp]

I agree but, until the users I'm supporting uninstall the older version, I have to support them with what they have.

that is why you need to install the VM to Your Pc.
Then you can develop, whatever version your client has.
You should adjust, not your client.
Mixing versions will cause you more headaches.

 

[burma]

I have no experience with this but take a look. Maybe it's something you can use?

Microsoft Access Version and Database Launcher: Total Access Startup ensures the right version is always started

Total Access Startup ensures the correct version of Access and your database are launched and installed properly. Easily deploy Access databases across a network and centrally manage them.

www.fmsinc.com

I would love to have that but my boss won't go for it (so far).

 

[burma]

$499 doesn't seem outrageous given that you need only a single copy of the application installed on a server and which ALL users use to launch their applications. I frequently have my clients purchase FMS products to help with things like this. It's a no brainer.

The alternative, is as the others have suggested is that YOU stick with the oldest version anyone has to you don't accidently use a feature that the older version doesn't support.

I agree that it's a good price for all it does, and FMS has a nice licensing model. In my case it's not about cost but the approved software acquisition channels my company uses. I've recommended other FMS products to them but so far no dice.

 

[Cotswold]

I used to have a folder off the root C:\ named as my company name. In that I would have sub-folders, one for each of my programs that the customer used. Then another folder in the company folder into which would be installed the Access RunTime. Each of the program folders contained the program FE and all of the necessary files for the FE to operate and open the BE. There was also a shortcut in each that opened the Access Runtime and as a parameter the individual program name. Each of the shortcuts were pasted to the Desktop.

I only developed and issued in one version of Access at a time. As I changed Access versions I updated my customers' systems. If any declined they would not receive any more updates until their Runtime and all of their programs were updated to my current version. I would never consider creating and issuing any MDE or ACCDE files over different Access versions of an application. I didn't experience any issues on any of the numerous sites that ran my software.

 

[Pete490h]

Access versions fight over control of the registry. So, the last version of Access you open takes control of the extensions it recognizes. There are two ways to solve the problem.
1. Always open the version of Access you want and then open the database - awkward and not functional for users.
2. Always use a shortcut that specifies the version of Access to open followed by the name of the Access database - much more user friendly for users.

As the programmer, I work with too many applications to keep shortcuts for each of them so I use option 1 for myself and only keep shortcuts for the apps I use rather than develop. So, the timekeeping app has a shortcut because mostly I will be using it rather than developing it.

Hi Pat,
I’m having the same problem…..
I upgraded to Access 2021 then uninstalled 2010 along with Access runtime 2010

The vbs script attached still tries to open Access 2010 ????
Any ideas

 

[The_Doc_Man]

There is the additional danger that if you have multiple versions of Access and inadvertently open the older front-end DB with the newer Access, you might update that DB so that the older version of Access will no longer work on it. The libraries get updated when you use a newer Access than the version under which it was developed.

 

[Isaac]

I agree. Now if I can get the client to agree ..

In the mean time, a solution other than opening Access first and then pointing to the file, would be welcome.

Can you Shell out the exe to the version you want to open, then use GetObject?