Splitting database.

[Guest]

A ouple of questions:

What is the preferred method of splitting the data base - before or after
implementing user level security? Should I use the wizard or do it manually
and how is it done manually.

What does 'distributing' my application involve? Do I just copy the front
end to each network machine and, if so, how does each copy remain linked to
the back end?

How do I amend permissions for the front end copies should I decide to
change them? Or do I just change them on the back end and the changes are
update automatically on the front end?

Thanx,

Rip

 

[Joan Wild]

A ouple of questions:

What is the preferred method of splitting the data base - before or
after implementing user level security?

You can do it either way, but I think after implementing security is easier.

Should I use the wizard or do
it manually and how is it done manually.

Don't use the wizard as the backend will be unsecure. Do it manually. See
http://www.jmwild.com/SplitSecure.htm

What does 'distributing' my application involve? Do I just copy the
front end to each network machine and, if so, how does each copy
remain linked to the back end?

Yes, just copy it to the workstations. The links are stored in the frontend
file, so travel with it. I suggest that when you link to the backend, use
UNC pathnames (use Network Neighborhood when you locate the backend), rather
than mapped drives, since users may not have the same mapping as you.

How do I amend permissions for the front end copies should I decide to
change them?

You make the changes in your copy of the frontend. Once you have them
finalized, you then distribute a copy to the users, overwriting their
existing frontend. You might want to consider using something like Tony's
Auto FE Updater http://www.granite.ab.ca/access/autofe.htm to automate this.

 

[Guest]

Thanx, Joan,

I read your 5 steps for database splitting on your site and it seems
(scarily) simple. What should I name the back end? Something like
MyDatabase_be, like the wizard does? Also, should I leave the name of the
front end unchanged? I imagine if the names are ever changed later, then the
linking won't work correctly, yes?

Also, I read somewhere that the mdw file should be located on a shared
network drive. It seems to me that putting it on each workstation with the
front end would be more efficient. Your thoughts?

Thanx again,

Rip

 

[Joan Wild]

Thanx, Joan,

I read your 5 steps for database splitting on your site and it seems
(scarily) simple. What should I name the back end? Something like
MyDatabase_be, like the wizard does?

Name it whatever you like, it doesn't matter.

Also, should I leave the name of
the front end unchanged? I imagine if the names are ever changed
later, then the linking won't work correctly, yes?

Correct, but you can just refresh the links (Tools, Database Utilities and
check 'prompt for new location').

Also, I read somewhere that the mdw file should be located on a shared
network drive. It seems to me that putting it on each workstation
with the front end would be more efficient. Your thoughts?

Not a good idea in my opinion. The mdw contains usernames/group
names/passwords. If you need to add a group or change a user's membership,
you'd need to do that in every copy. If you just send the changed mdw to
each user, you'll overwrite their password. You'll find it much easier to
maintain a single mdw file. Don't name the backend the same as your mdw
file - they each need to create their own ldb file.