Hi there.
I created an add-in in accde format.
This add-in uses databases internally.
The contents of internal databases are editable while using the add-in.
I thought that when the add-in was opened several times at the same time, each time we had an independent.accde file with its own management of these databases.
My bad.
I found that internal databases were common to all open add-ins.
So I end up with a problem when multiple databases using the add-in are open at the same time. When switching the selection from one database to another, the internal data of the add-in no longer corresponds to the selection?
Can you advise me on the best possible solution?
In my case, shouldn't the opening of the add-in be prevented if it is already open in another database?
THANKS
I created an add-in in accde format.
This add-in uses databases internally.
The contents of internal databases are editable while using the add-in.
I thought that when the add-in was opened several times at the same time, each time we had an independent.accde file with its own management of these databases.
My bad.
I found that internal databases were common to all open add-ins.
So I end up with a problem when multiple databases using the add-in are open at the same time. When switching the selection from one database to another, the internal data of the add-in no longer corresponds to the selection?
Can you advise me on the best possible solution?
In my case, shouldn't the opening of the add-in be prevented if it is already open in another database?
THANKS