MS-Access XP frontend corrupting

D

Duncan Dimech

Dear All,
I have coded a system which is in use by three companies. The system is a
real estate catalogue management tool. It is written entirely with
Ms-Access XP and it has been split as a front-end and as a backend and it
has been secured through the MDW security file. The system works well in
two companies but I have some problems with the third. All three companies
have the same installation - a mapped drive which we call Z: and a number of
folders including front-end and backend in the Z drive. The front-end
directory contains the front-end of the system while the backend contains
the backend. Apart from these I have a MDW, images and audit folders which
contain the relative files.

The problem is this - The third company and only the third has 23 employees
(the other have only 5 users) but only 12 log contemporary as there are only
12 machines available and all employees have the right to enter data. Data
is entered from unbound forms and when they press the SAVE and EXIT button,
the system saves the data through and an ADO connection. While editing and
browsing data is retrieved using bound forms.

This works fine but sometimes (even 5 times a day) the front-end at the
third company corrupts and a compact and repair is needed.

Any form of information will be appreciated

Thanks and Regards
Duncan Dimech
EXOR Group
 
D

Duncan Dimech

Dear All,
the table from which the report has to be generated is an audit table and is
made up of the following fields
UserName
Date
Time
Action
ActionDetails

thanks and regards
Duncan Dimech
EXOR Group
 
M

Marshall Barton

Duncan said:
Dear All,
I have coded a system which is in use by three companies. The system is a
real estate catalogue management tool. It is written entirely with
Ms-Access XP and it has been split as a front-end and as a backend and it
has been secured through the MDW security file. The system works well in
two companies but I have some problems with the third. All three companies
have the same installation - a mapped drive which we call Z: and a number of
folders including front-end and backend in the Z drive. The front-end
directory contains the front-end of the system while the backend contains
the backend. Apart from these I have a MDW, images and audit folders which
contain the relative files.

The problem is this - The third company and only the third has 23 employees
(the other have only 5 users) but only 12 log contemporary as there are only
12 machines available and all employees have the right to enter data. Data
is entered from unbound forms and when they press the SAVE and EXIT button,
the system saves the data through and an ADO connection. While editing and
browsing data is retrieved using bound forms.

This works fine but sometimes (even 5 times a day) the front-end at the
third company corrupts and a compact and repair is needed.


Did you say that all the users are sharing a single copy of
the front end mdb file? If so, that is a very risky
arrangement. Each user should have a copy of the front end
installed on their local machine.

Even though you didn't commit the sin of multiposting,
please don't crosspost to so many newsgroups.
 
A

Albert D. Kallal

As a few others has mentioned, you REALLY do NOT want multiple users in the
same front end.

The best approach is to have a copy of the front end on EACH pc. Further,
you should be use a mde, and further to that, you should use unc path names,
as often the drive mapping can change if things like a cd rom, or other
drives are installed on those client pc's. By using unc path names, you
NEVER have to care, or worry about drive mapping. Besides, drive mapping is
a old throw back to the old dos days..and you should avoid it as it will
also reduce the number of service calls you receive.
 
D

Duncan Dimech

Thanks to all those who replied
The recommendations you gave are precious and they here is a summary

Frontend for every user
Mde and not mdb - I only supply mde sorry not to mention in my mail
use unc instead of drive mapping

with regards to the unc - how I am going to set the unc for each and every
client differently for linking tables?

Thanks and Regards
Duncan Dimech
EXOR Group
 
A

Albert D. Kallal

When you link the file *just* before you distribute, you can use network
neighbourhood when you link. Browse to the back end using that process, and
you will thus use unc.

If the client pc has access to the folder where the back end resides, then
using unc will work EVEN when the drive mapping is changed, or messed up, or
even in fact NO drive mapping is done at all! (this is why we avoid the
drive mapping dance anyway).

After you link, you can take a look at the path names of the back end by
using the linked table manager again. The format of UNC is of course:

\\serverName\folder\YourBackEnd.mdb

Also, if you need a process to keep every client computer updated with the
latest version, then Tony has a nice free auto front end updater at:

http://www.granite.ab.ca/access/autofe.htm

Good luck!
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top