Search results

Here are the findings. I used an A2013 .accde and an A365 .accde On a pc running Windows 11, I had installed Office 2013 (including A2013) and A2013 Runtime. I installed A365 with no problem and I ran the program using a shortcut whose Target was something like C:\AppDir\AppName.accde /Runtime...

Colin's article in #5 is useful, but could not find an answer to the specific question, "can the A2013 and A365 Runtime coexist?" I have today prepared a new pc and I will try it out and will report. BTW, not everyone wants to have Office on their PC, so having both Runtimes is a solution for...

Let me shed some light on this with a real problem at hand. We have a software package stored in probably 200 locations and this works fine the A2013 Runtime. The software package is as complicated as it gets and we cannot remain forever in A2013, due to tableID restrictions etc. We will move...

Can A2013 Runtime coexist with A365 Runtime? More specifically, if A2013 Runtime already exists, can the A365 Runtime be installed?

I apologize for being unable to explain a simple thing. 1) In the FE you can have data common to all clients. You can have this data stored in the BE, but since it is not specific to a specific client and does not change, the FE is preferable to the BE. As an example, you can store all the...

The data in the FE is basically the same for all users. As I mentioned not all users have the latest FE, but this does not affect their operation. If all clients get the latest FE , they will have the same FE. There is no risk.

"UserA" does not update his copy of the FE. He may use the Static data common to all users and the Temporary tables that can be helpful to creating Forms and Reports. The users may operate on different versions of the FE, assuming the FE is properly constructed so that when it is copied to a...

You can also put Temporary tables in the FE. Sometimes Temporary tables are used as the record source for forms and reports. The Temporary table is filled in with the relevant data. Yes you can skip Temporary tables, but many times they help debugging since you have a clear picture of the...

As I mentioned the client list can for example contain the expiry date of a specific client's subscription. After the client pays his subscription this date is changed and the client downloads the new FE. And yes you can keep data that is common to all users in the FE. As an example, let's say...

I have tried almost everything, the add-in may be useful if you are so kind to provide it.

Do you know the Access version that has the increased TableID number

The problem is that the older versions do not support the required TableID number.

You can keep data in the FE that is common to all users. You can also keep a list of all your clients together with the date when their subscription ends. When your client renews that date will be updated. T

I created the .accde in A365 and appears to be working in A2013. 1) Does anyone have practical experience in creating a .accde in A365 and afterwords working in A2013? 2) Is there a way to view the number of TableIDs created during the creation of a .accde? 3) Is there a practical way to...

The TableID limit may be the problem since I am able to create .accde for smaller DBs in A2013

Good to know. It did not appear to make a difference in my case. If push comes to shove as a temporary solution I can rename the accbd to accde, so that the client has continuity. I would just need a new way to lock the software the software. Hopefully, it will not come to that. I have also been...

I have fixed all the Option Explicit and I am still getting that my .accdb is in use. I will also check the api declarations. I could post the entire code around 80Mb.

In other words, do not interrupt the creation of DATABASE.mdb in any way. Wait for it to "cool down"

Is it advisable to interfere with its creation, like deleting all Access processes? What would happen if all Access processes are deleted in the process of the creation of DATABASE.mdb?

I will make sure that the Option Explicit is placed in all modules, forms, reports. If it is not present then it can compile but may cause problems. So it has to compile with Option Explicit present to be on the safe side. When I close my .accdb the locking file will close if no-one else is...