Questions on splitting

[Guest]

I've read thru many of the posts and still had a few questions regarding
splitting. Currently, I have a secured database. Using Joan's suggestion, I
made two copies of the database (BE/FE) and deleted the tables from the FE
copy and linked them to the BE copy.

Is there a reason why I can't keep all the queries, forms, etc...on the BE
query? I can use this copy as a "master" copy of the database, make design
changes, and export the objects out to the FE copies. Not being an
Access/computer/IT guru, I am uncomfortable with using a program like Tony's.


If exporting design changes to the FE copies, will I lose the user security
sitting on each FE copy?

When creating the FE copies, do I need to give each a different file name?

Can I just store the FE copies on one common server, thus avoiding having to
deploy the FE copy out to each person's desktop?

If not, is there an easy way to deploy the FE copies to the users and have a
way for them to automatically create the shortcut on their desktop?

Thanks in advance!

 

[Rick Brandt]

I've read thru many of the posts and still had a few questions
regarding splitting. Currently, I have a secured database. Using
Joan's suggestion, I made two copies of the database (BE/FE) and
deleted the tables from the FE copy and linked them to the BE copy.

Is there a reason why I can't keep all the queries, forms, etc...on
the BE query? I can use this copy as a "master" copy of the
database, make design changes, and export the objects out to the FE
copies. Not being an Access/computer/IT guru, I am uncomfortable
with using a program like Tony's.

Using Tony's tool does not require "Guru" status.

If exporting design changes to the FE copies, will I lose the user
security sitting on each FE copy?
Yep.

When creating the FE copies, do I need to give each a different file
name?
Nope.

Can I just store the FE copies on one common server, thus avoiding
having to deploy the FE copy out to each person's desktop?

You can, but then you are throwing away most of the benefits of splitting in
the first place.

If not, is there an easy way to deploy the FE copies to the users and
have a way for them to automatically create the shortcut on their
desktop?

How big is the front end file and how fast is your network? In some cases
the time required to copy the file from your master location is so small
that you can forget about "versions" and just copy the file every time it is
opened. All you need is a batch or script file that copies the file first
and then opens it. If the file is large enough for that to be a problem
then Tony's tool is the best solution you've got.

 

[Immanuel Sibero]

Hackmn_g

Some comments inline

Immanuel Sibero

I've read thru many of the posts and still had a few questions regarding
splitting. Currently, I have a secured database. Using Joan's suggestion, I
made two copies of the database (BE/FE) and deleted the tables from the FE
copy and linked them to the BE copy.

Is there a reason why I can't keep all the queries, forms, etc...on the BE
query? I can use this copy as a "master" copy of the database, make design
changes, and export the objects out to the FE copies. Not being an
Access/computer/IT guru, I am uncomfortable with using a program like

Tony's.


Not recommended. You will have problems making changes to the queries,
forms, while the BE is in use.

If exporting design changes to the FE copies, will I lose the user security
sitting on each FE copy?

Never done it this way. Not being an Access/computer/IT guru, why do this
the hard way? Keep a copy of FE as a template, this is the one you make your
changes, improvements, etc. Once you're done, simply give a copy for each
user. No export, import necessary.

When creating the FE copies, do I need to give each a different file name?

No. Use the same file name and each user should have a local copy.

Can I just store the FE copies on one common server, thus avoiding having to
deploy the FE copy out to each person's desktop?

Well, the ideal setup would be each user's desktop. When you use Excel or
Word, etc., you would put the documents and spreadsheets on the server and
you would install Excel and Word (i.e. user apps) on each user's desktop,
wouldnt you? Pretty much the same logic for Access.

If not, is there an easy way to deploy the FE copies to the users and have a
way for them to automatically create the shortcut on their desktop?

Tony's FE Updater is the easy way.
You can also look into installer utilities. But Tony's FE Updater was
written so you dont have to deal with the complexities of installer
utilities.

 

[Guest]

Rick and Immanuel:
First, thank you for your first responses. Some follow up questions, if you
don't mind.

To deploy, are you both saying that all I have to do is send an email out to
each user and attach the FE database and the shortcut (to point them to the
right Secured.mdw file)? Instruct them to just detach the files and copy to
their desktops? If done this way, would I then have to change the shortcut
to point to the FE database on their desktop? With the BE on the server, all
I would need to insure is that their network mappings are pointing to the
right server drive?

In response to your question, Rick. The FE file won't be bigger than 12MB
and our network is pretty quick and reliable. You mentioned copying the file
everytime it's open by using a script file. How would I have each user's
computer copy the FE master file sitting on the server? Do you have this
script and can you tell me where it would have to be installed?

Thanks again!!!

 

[Rick Brandt]

Rick and Immanuel:
First, thank you for your first responses. Some follow up questions,
if you don't mind.

To deploy, are you both saying that all I have to do is send an email
out to each user and attach the FE database and the shortcut (to
point them to the right Secured.mdw file)? Instruct them to just
detach the files and copy to their desktops? If done this way, would
I then have to change the shortcut to point to the FE database on
their desktop? With the BE on the server, all I would need to insure
is that their network mappings are pointing to the right server drive?

I wouldn't mess with putting the file on the desktop. Just put it in a
common (simple) location like C:\YourAppName\YourFile.mde

If everyone puts the file in this same location then it is easy to give them
all a shortcut that they CAN put on their desktop to launch the app because
the target for the shortcut will be the same for all users.

In response to your question, Rick. The FE file won't be bigger than
12MB and our network is pretty quick and reliable. You mentioned
copying the file everytime it's open by using a script file. How
would I have each user's computer copy the FE master file sitting on
the server? Do you have this script and can you tell me where it
would have to be installed?

Using the example location above you could have a batch file with...

Copy \\Server\ShareName\YourFile.mde C:\YourAppName\YourFile.mde /y
Start C:\YourAppName\YourFile.mde

I do this on one of our Terminal Servers to execute a 20MB file, but it has
a GigiBit ethernet connection between the Terminal Server and the server
where the master copy is published. Whether it's a good idea for you would
also depend on how the file is used. If users tend to open it early in the
day ands leave it open then it's not a bad strategy. If they tend to open
it, use it for a few minutes, and then close it, repeating many times during
the day, then it might not be a good idea to be doing all of that needless
copying.

 

[Guest]

Rick,
Thanks much! The example batch file...where would that be attached? In
other words, how would Access know to copy the latest FE file each time a
user opens up their copy of the FE database?

 

[Rick Brandt]

Rick,
Thanks much! The example batch file...where would that be attached?
In other words, how would Access know to copy the latest FE file each
time a user opens up their copy of the FE database?

Your user's shortcut would run the batch file not the Access file.