Implications of DB Split 2

[RosieMP]

I was wondering if anyone could offer an overview of post-split administration of an Access DB. I'm facing doing my first split and I've read enough about the process of how and why to do it to feel confidant, but I'm having a hard time envisioning what it's like to make changes to the database after the split--like when someone comes along and decides they want a new report, or a new search option on the main form.

Could someone tell me if I have this right:
1. I split the DB using the database utility. I wind up with a front end and back end.
2. I put the back end out on the network, and deliver (let's say I send it via email) the front end to my users. I can then make changes at individual workstations, i.e, a manager's delete button is visible but maybe their staff doesn't have access to the same button.
3. I keep a copy of the front end in some safe place. This is my master copy. Should someone decide they want a new report, I add it to my master copy of my front end and then redistribute the front end to the users via email and make sure they overwrite their old copy.
4. If someone decides, which they absolutely won't, because we've fully covered this at this point and everyone understands that it's in our best interest to get the data right before we go live (right? right???) I make the change to the back end, whatever changes are necessary to the front end, and the redistribute.

Basically I have a master copy of the front end I hold and make changes to, probably a copy of the back end as well just so I have a back up of relationships, and I make changes and redistribute as needed.

Do I have this right, and are there any issues, logistical or otherwise, I might be missing?

Thanks for all insights & advice.

 

[Remou]

You may wish to make the front end into an mde, however, there can be problems if people have different versions of Access. You may wish to ensure that you use late binding to avoid problems with referencing additional libraries. People often prefer to use, say, a vbscript file to open the front-end; such a file can check if a new front-end version exists and copy it across from the server. If you wish different people to have different levels of access, you may wish to consider Access security, rather than several front-ends.

 

[Ed2020]

Yes, it sounds like you have the right concept.

One problem you will need to address is how to ensure users are accessing the correct version of the frontend.

My solution to this is to have a version table in the backend and a version table in the frontend. The backend table is linked into the frontend. Whenever you make a change add a new version number to *both* tables. On system startup run a validation to check both numbers are the same - if not display a warning and quit the application.

I'd also recommend against not distributing new frontend versions over email - put it in a central location that all users have access to and have them copy the file to their local drive. Better still create an installer (just a simple batch file?) to copy it for them.

Ed Metcalfe.

Please do not feed the trolls.....

 

[RosieMP]

Thanks very much to both of you.

Remou--can you clarify re. making the .mde file? I thought that happened automatically when I ran the utility.


Re. Security -- I'm a little intimidated by workgroup/security/administration functions and haven't done much research into them. Can either of you suggest a place for me to start looking into it? I'm a little disinclined to add an additional complicating layer onto the project--and I'd like to think it isn't necessary in this particular project, but it's something I need to become familiar with.

Thanks again.

 

[Remou]

If you make mde's you will need to test them on each version of Access that will be used. If you specifically reference a library, the reference will remain in the mde.

Depending on the versions of Access you will be using, you may need to consider signing your code:

http://office.microsoft.com/en-us/access/HP010397921033.aspx

The Access FAQ is a good place to get an idea of what is involved:

http://support.microsoft.com/default.aspx?scid=/support/access/content/secfaq.asp