Multi user problems

[Guest]

Hi,

I have DB that is being used by at least 10 people at a time, adding about
500 records per week. I havent split it yet for verious reasons. But I've had
loads of probs with and lost some data, so I'm looking to make sure this
never happens again. The DB died on me saying that it needed repairing and it
just deleted aroung 200 records for no reason. I'm gonna split it and repair
it at least once a week. I have a few questions.

Do I have to repair the back end or just the front end, and is it best to
set these to repair on close?

I know I will have to make changes to the front end, whats the best way to
update users? I cant install any new software on these PCs. Short of telling
the users to copy the file themselves when there has been an update, I cant
think of a good way to do this.

Can repair and compact delete records? Seriously, I'm sure this has happend
to me. Can having a password on the DB effect repair and compact?

 

[G. Vaught]

Don't repair the database unless it specifically tells you. Do Not Set Any
of the databases to "Compact on Close". When you compact/repair the
database, every user must be out of the database otherwise you could corrupt
your database beyond recovery.

You should not lose records from repairing/compacting the database. Are you
sure they are lost? Don't confuse the previous size of the database to the
current size after a repair, because it may also compact the database to a
smaller size. You may have lost records due to the database being corrupted
or the data never made it to the database in the first place.

If you split the database and place the backend (tables only) to a server
type machine and place the front-end on each user's machine, you should not
have to worry about a repair at all. What you will do is compact the
database periodically. Depending on which version of Access, this may be
combined with a repair. I would do this at least once a month, twice a month
if you add more than 2,000 records a month.

If you update the frontend, then you can have the user's copy the update to
overwrite their previous version. They won't have to install anything. With
a little ingenuity you could probably write a batch file that would copy the
new version to their machine. You would have to make sure they have closed
the database on their machine first before executing a batch copy.

 

[Albert D. Kallal]

Do I have to repair the back end or just the front end, and is it best to

set these to repair on close?

I am sure you have a rigorous back system, and a good backup is done every
day.

You will have to assign the job of database administration, and compacting
to
your database administration staff. This person will be responsible for
ensuring
that the database is backed up on a regular bases, and also that
compacting is done on a regular bases also. How often these procedures will
be done is going to depend on how much volume, and use the back end data
file see. Regardless, you do have to schedule and assign this task to
someone,
as a front end does not compact a back end. And, further, you don't want
just
any old user on the system doing anything they please and having the
back end compacted. Compacting is a very resource intensive operation, and
can sersouly impact the network.

I know I will have to make changes to the front end, whats the best way to
update users?

Well, I could as you as a developer, what would you do? I mean, how did you
work on bug fixes, and the next update/great version of software wile users
are currently working? You caj't psobliry tell all the workers to go home,
or not use the apcton?. Splitigng is not only is more reialiry, and a
requement for multi-users operation to reduce curruptions, but spliting also
supports the whole devepument process like milk goes with cookies!

Anway, the easy sotion here is to grabs Tony's auto Front end udpateer:

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

Another sotion is to simply spend less then a hour of your time, and write
your own code that checks for a udpate, and if it finds one, copes the new
mde applcation from the server to the users pc. However, Tonny's got a nice
soltion, and he is sharing it. And, while we are at this...you do distrbitoe
a mde to each user...right?

Without quesiton, no one is suggesting you run aounrd with a floppy disk and
install the new updates!! In some cases, I zhave emaled users a zipped filoe
that automailry un-zips to the corect dir. There is TON of sotions to this
problem, and which soltion you choose is going to ber based on your needs. I
also in addtion to using winzp, and my custom code, I also use the open
souce Inno installer, and it is also very usefaul.

However, for most solutions, my vote is for Tony's updater...it really is a
gem..

I cant install any new software on these PCs. Short of telling
the users to copy the file themselves when there has been an update, I
cant
think of a good way to do this.

Well, Ton'ys updater will solve this problem. And, as a devleoper, you could
rool your own sotion here. Anway, in fact, you do DO NOT even have to
install Tony's solution n each pc!.

Can repair and compact delete records? Seriously, I'm sure this has
happend
to me.

Hum, I suppose this could happen if some records are damaged, it might be
the case.

Can having a password on the DB effect repair and compact?

No, I see nothing here that would be of any relevance.

 

[Joseph Meehan]

Hi,

I have DB that is being used by at least 10 people at a time, adding
about 500 records per week. I havent split it yet for verious
reasons. But I've had loads of probs with and lost some data, so I'm
looking to make sure this never happens again.

Never say Never. &*%^ happens. However a lot less will happen if you
split the database. Chances are many of the problems you have had are
because it is not split.