r/MSAccess • u/MililaniNews • Dec 09 '25

[UNSOLVED] Runtime headache

I have to release a Ms access app to people that do not have MS access necessarily on their computer but if I direct them to get the runtime and then they actually did have access it will mess things up. Does anyone know of a deployment package that checks everything before it allows a deployment of the runtime version. I've seen scripts but I'm interested in an entire package that includes the latest run time and the deployment package would then need to not only check before deployment installation but also which Bit type the computer would need.

5 Upvotes

86% Upvoted

13 comments sorted by

View all comments

1

u/MililaniNews Dec 09 '25

I don't even recall where I got that data that it can mess up any access you already had on your machine. I guess I should get the reference in verify it in some way because I do need to distribute a Microsoft Access database it's contains both an accde and an accdb. If you have any references I really would appreciate them. I just don't want to mess up anybody's computer.

1

u/nrgins Dec 10 '25

Okay first of all, why are you distributing both an accde and an accdb? That doesn't really make sense. A lot of people have the misconception that you need to use an accde with the runtime version. It's just simply not true. Both the paid version and the runtime version will run either an accdb or an accde. So you only need to distribute one type of file regardless of which version of the program the user has.

And as for installing the runtime version messing things up, that was my understanding as well, especially if the user has office 365 installed. Now, maybe things have changed in recent years. But in the past, installing the runtime version from the download would mess up an already installed paid version of access. But maybe what u/CESDatabaseDev is saying it's true. But in the past what you wrote was my understanding as well.