Question ACCDE and Structure Changes

[gary.newport]

I have a database that I have converted into an ACCDE file to help reduce the size of the actual implementation. I am aware that if I want or need to add/edit any forms, queries, tables, etc then I would need to do this to the original source system.

My concern is; what if my ACCDE system has been used and the data changed? How do I make changes without losing the data when I next save the ACCDE or is there a way of ensuring that the data between the ACCDE and the original file is synchronised properly before any changes are saved?

 

[SOS]

You should have a SPLIT database (backend holds the TABLES) and then the FRONTEND (should have everything else) so you don't have to worry about the data. Plus each user should have a copy of the frontend on their machine (don't share a file across the network).

 

[gary.newport]

I have just read a similar line and see this as the first solution (the splitting of the system into two parts).

As regards your second point. Many of those using the system have their own laptops and it is difficult enough for many of those to find a single location on the one and only network shared drive on the entire network (T:\activities). Trying to get them to find a local copy would be nigh on impossible.

 

[SOS]

As regards your second point. Many of those using the system have their own laptops and it is difficult enough for many of those to find a single location on the one and only network shared drive on the entire network (T:\activities). Trying to get them to find a local copy would be nigh on impossible.

Well, I just want to warn you that sharing a frontend WILL result in corruption of the frontend. It isn't a matter of IF, but only a matter of WHEN. Also, you will find that people have problems connecting with it and sharing issues. So, if you want to deal with the headaches you can, but it will keep your sanity much better if you just have each person have their own copy (you can use Bob Larson's free Frontend Auto Update Enabling Tool to make it easy to maintain the frontends on each user's machine. You deploy the database frontend ONCE and from that point on it is automatic. I would highly suggest teaching your users how to click a shortcut on their desktop to open the database and then save yourself a major headache.

 

[gary.newport]

I have started to follow your advice in it's entirety; thanks.

I split the data from the forms, queries and reports. I have linked the tables across and everything works fine. I then downloaded the update tool and followed all instructions to the letter.

The code does not run unless I convert the system into an ACCDE. If I do this I get an error message stating that it cannot find the tables that are, in fact, in the Master FE and Maste BE files. I have gone through the code I added to the OnLoad instruction for the Switchboard and I have gone through the added module that the update tool creates but I cannot see where the global variable values are being assigned; and this I believe is the issue!

Any ideas?

Also, am I correct that the code does not run unless it is in ACCDE form (rather than ACCDB) or am I missing something else?

I placed a breakpoint on the opening line of the code and it did indeed stop and then come up with the error message (as an ACCDB) but if I run the system without the breakpoint then I get no error message but I also get no updating; regardless of me changing the version number in the two master files.

 

[SOS]

1. Make sure you have a trusted location set and that the database file is in that location.

2. As far as the missing table, if I remember correctly there is a table that gets put into the backend by the tool and you then have to link to it from the frontend (manually) so that it can be seen by the frontend.

 

[gary.newport]

Yep, this was all sorted by the very kind Bob who built the system in the first part. I hadn't linked it across. We are now rolling out your solution ready for next week!

Thanks very much.