Making changes on Front End Design 2

[VOGEL24]

I am wanting to split a database into Front End Back End but I have some questions before I do this. I have read a little about splitting and I know how to secure a database but I want to do it the best way the First time around.

1. What is the easiest way to update multiple Front Ends after any changes are made to Forms, Reports etc.? I know that I can Copy (My) Front End to each station after any updates. But then I have the issue of next question.

2. I am the only one that changes or adds Forms but users can create their own reports. If I update users Front End with (My) Front end then their reports will be gone. Right?

3. How does a secured database work with Front End Back End?
Do I secure the database before I Split it or Secure each Front End copy after I Split? (I have not secured yet)

Any Help would be appreciated.

Mary

 

[chris153]

Hello,

1. Try setting up a batch file, which copies the secured front-end from a network drive onto the users PC, e.g.

xcopy {location and name of front-end} c:\ /e

copy this into notepad and change the file extension to .bat, double click on the file to run it.

2. I'm afraid so, you could set-up another front-end with links to the back-end so that users can build reports in there and it wouldn't get copied over when you re-distribute.

3. I generally keep an unsecured database that only I can access for development purposes and only secure it before re-distribution.

Hope this helps

 

[randy700]

Rather than copy the entire new front end, why not create a routine that will only copy the forms, modules, reports, etc that you have updated. You would, of course, need to include a step to delete those same objects prior to importing the new ones.