Where Should The Front End Live?

[E.Q.]

Hi,
I have my database configured and split it, actually creating two front
ends; one for my employees and one for my fellow supervisors and myself.
I can envision the employee copy being used mostly on three PCs (though I
can think of 6 that might potentially be used). Similarly, the front end for
the supervisors would likely be used on one of five PCs (though again about
12 others might be used).
Right now I only have one copy of each on the network. For now, I don't
think there will be a lot of times when we'd have multiple users. Though the
bosses in two other departments have expressed an interest in having the
database as a tool to track the training in their departments as well. (But I
would have no access to their PCs; I'd have to convince IT to help at that
point.)
I'm not sure where to put the front ends. Since the database might be
distributed to machines that I don't have access to I thought that keeping it
on the network would allow me to tweek it when needed.
What are my options here? What kind of problems might I run into if I just
have one copy of each front end and have the users access those?
Peace.
EQC

 

[Beetle]

You definitely should not be doing it the way you are. Having multiple users
share the same FE is one of the most frequent causes of database corruption.
Each user should have their own copy of the FE on their local hard drive. If
you
use UNC path naming for the link to the back end, as opposed to drive letter
path naming, then you should not have to re-link to the BE everytime you
give a new user a copy of the db. Your IT department should easily be able
to help you intall new/updated copies through the network when it is
necessary.
Keep a "master copy" on your own hard drive for making design changes, then
make a copy to distribute to your users. I even keep a copy of the tables on
my
local hard dive (not all the data, just the structure and some example data).
When I am making design changes, I have it linked to my local BE because
it's faster when you're running new queries, etc. Then I make a copy of the
new FE, re-link it to the network BE, then distribute updated copies to the
users.

 

[E.Q.]

Thanks.
I've saved a copy of both front ends to my hard drive and I'll do the same
on the two machines that I've created desktop shortcuts for demonstrations
purposes.
Most of my users won't find the file without a shortcut.
I'm thinking that I'll leave a copy of each file on the network so I can
install them. I'll just change the password to one that isn't widely used in
our department. That should prevent multiple users.
I'll see what IT can do to help.... They're quite busy with a switchover of
our accounting software.
Peace.
EQC

 

[Tom Wickerath]

Hi E.Q.,

To add some to Sean's answer, which I am in 100% agreement with, please see
the following article:

Implementing a Successful Multiuser Access/JET Application
http://www.accessmvp.com/TWickerath/articles/multiuser.htm

The only things your IT Department should need to assist with are ensuring
that all users have RWCD privileges for the shared folder, and perhaps
helping to verify that all service packs have been installed for the
operating system, Office, and the JET database engine on each PC that will be
used to open your application. This article provides more background on the
need for each user to have the correct folder privileges:

Introduction to .ldb Files
http://support.microsoft.com/?id=299373

These articles provide information to help you determine if each machine is
properly updated:

How to keep a Jet 4.0 database in top working condition
http://support.microsoft.com/?id=303528 In particular, follow the
three links:

Verify that the latest operating system service pack is installed
Verify that the latest Microsoft Jet service pack is installed and
Verify that the latest service pack for your version of Office is
installed

Also recommended: Install the latest version of MDAC (Microsoft Data Access
Components
http://www.microsoft.com/downloads/...e3-c795-4b7d-b037-185d0506396c&DisplayLang=en

(But I would have no access to their PCs; ...
and

Since the database might be distributed to machines that I don't have
access to I thought that keeping it on the network would allow me to
tweek it when needed.

Do the initial installation with the user present and logged in. I highly
recommend that you spend some time learning Access MVP Tony Toews' free
"AutoFE Updater" utility. This utility eliminates the pain associated with
updating local copies of the FE application. It is mentioned in my Multiuser
Applications paper.


Tom Wickerath
Microsoft Access MVP
http://www.accessmvp.com/TWickerath/
http://www.access.qbuilt.com/html/expert_contributors.html
__________________________________________

 

[John W. Vinson]

Hi,
I have my database configured and split it, actually creating two front
ends; one for my employees and one for my fellow supervisors and myself.
I can envision the employee copy being used mostly on three PCs (though I
can think of 6 that might potentially be used). Similarly, the front end for
the supervisors would likely be used on one of five PCs (though again about
12 others might be used).
Right now I only have one copy of each on the network. For now, I don't
think there will be a lot of times when we'd have multiple users.

Once is enough to corrupt the database, if youj're at all unlucky.

Though the
bosses in two other departments have expressed an interest in having the
database as a tool to track the training in their departments as well. (But I
would have no access to their PCs; I'd have to convince IT to help at that
point.)
I'm not sure where to put the front ends. Since the database might be
distributed to machines that I don't have access to I thought that keeping it
on the network would allow me to tweek it when needed.

Keep a clean copy of the frontend on the network, and download it to the
machine of each user who needs access to the database. Tony Toews has a
program to automate this - check at
http://www.granite.ab.ca/access

What are my options here? What kind of problems might I run into if I just
have one copy of each front end and have the users access those?

Bloating, bad performance, risk of corrupting the frontend, lockups... do you
need more?

 

[E.Q.]

Thanks.
You've given me some good resources. One of your links even gave me an
answer for not using memo fields. I had been told to avoid memo fields but
didn't know why. In both this database and another I made, I use text fields
for comments and was challenged regarding why I would limit those entries. (I
now have another reason perhaps more valid than my preference to limit
loquacious notes.)

BTW the following link didn't work.
How to keep a Jet 4.0 database in top working condition
http://support.microsoft.com/?id=303528 ;

As to my project, the back end sits in a new folder in a very public folder.
I've asked IT to set up privileges to prevent an accidental deletion but
still allow data entry.
I'll see what we have with regard to MDAC and the other utilities/updates
you mentioned.
Thank you.
EQ

 

[Tom Wickerath]

Hi E.Q.,

I'm glad I could be of help to you!

BTW the following link didn't work.

Strangely enough, it worked fine in your reply, but not in my post. That's
what I get for copying it from a Word document and pasting it into my
newsgroup replies <sigh>. When I clicked on this link in my posting, I see
the following in the address bar:

http://support.microsoft.com/303528 

Delete this junk at the end: %c2%a0
In case you'd like a copy of the Word doc. I used, you can download a zipped
copy from this location:

http://www.accessmvp.com/TWickerath/downloads/accesslinks.zip


Tom Wickerath
Microsoft Access MVP
http://www.accessmvp.com/TWickerath/
http://www.access.qbuilt.com/html/expert_contributors.html
__________________________________________

 

[aaron.kempf]

no, that works--
of course; I think that pertains to just about anything that anyone
does in JET.

I'd just reccomend moving to SQL Server

 

[Tom Wickerath]

Hey Aaron,

Why don't you take your vast knowledge of SQL Server, and go answer
questions posted on a SQL Server newsgroup? You'll probably feel better too,
since you won't have to continually tell people who are already using SQL
Server how crappy JET is.


Tom Wickerath
Microsoft Access MVP
http://www.accessmvp.com/TWickerath/
http://www.access.qbuilt.com/html/expert_contributors.html
__________________________________________

 

[Beetle]

I occasionally see questions related to SQL Server in the Access newsgroups,
although I don't see Aaron answering many of them. Wonder why? He must
be too busy hammering out mostly useless replies like "JET sucks"

 

[Tom Wickerath]

Sean,

Your reply just earned you a "greenie" <smile>


Tom Wickerath
Microsoft Access MVP
http://www.accessmvp.com/TWickerath/
http://www.access.qbuilt.com/html/expert_contributors.html
__________________________________________

 

[Alan]

Hi,
I have my database configured and split it, actually creating two front
ends; one for my employees and one for my fellow supervisors and myself.
I can envision the employee copy being used mostly on three PCs (though I
can think of 6 that might potentially be used). Similarly, the front end for
the supervisors would likely be used on one of five PCs (though again about
12 others might be used).
Right now I only have one copy of each on the network.  For now, I don't
think there will be a lot of times when we'd have multiple users.  Though the
bosses in two other departments have expressed an interest in having the
database as a tool to track the training in their departments as well. (But I
would have noaccessto their PCs; I'd have to convince IT to help at that
point.)
I'm not sure where to put the front ends.  Since the database might be
distributed to machines that I don't haveaccessto I thought that keeping it
on the network would allow me to tweek it when needed.
What are my options here? What kind of problems might I run into if I just
have one copy of each front end and have the usersaccessthose?
Peace.
EQC

Hi,

If necessary, I think you can try a utility called Advanced Access
Repair to repair your Access MDB file. It works rather well for my
corrupt Access MDB files. Its web address is http://www.datanumen.com/aar/

Alan

 

[Tony Toews [MVP]]

If necessary, I think you can try a utility called Advanced Access
Repair to repair your Access MDB file. It works rather well for my
corrupt Access MDB files. Its web address is http://www.datanumen.com/aar/

You also work for that company. Posting without disclosing any
connection is highly unethical and sleazy.

Tony

--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/