Causes of Corruption??

[Bill]

Hi All,

I have setup a shared secure database using an mdw file and a batch file to
launch. The database has been working fine for several months now but today
for the second time it has corrupted.

The nature of the corruption varied but in each case I reckon we could have
been in a situation where one or two users were accessing the mdb file AND
somebody copied the mdb file.

Could that have caused the corruption or are there other know causes that I
be pointed at please?

Ta.
Bill.

 

[Keith Wilby]

Hi All,

I have setup a shared secure database using an mdw file and a batch file
to launch. The database has been working fine for several months now but
today for the second time it has corrupted.

The nature of the corruption varied but in each case I reckon we could
have been in a situation where one or two users were accessing the mdb
file AND somebody copied the mdb file.

Could that have caused the corruption or are there other know causes that
I be pointed at please?

It's commonly said that multi-users on a shared file will cause corruption.
Is your application split?

Keith.
www.keithwilby.com

 

[Bill]

It's commonly said that multi-users on a shared file will cause corruption.
Is your application split?

Keith.
www.keithwilby.com

No, why would that help?
Is it considered better for the application to be in one mdb file and the
data in another mdb file.
How would that work with security delivered via an mdw file?
Regards.
Bill.

 

[Keith Wilby]

No, why would that help?

It would reduce the risk of corruption.

Is it considered better for the application to be in one mdb file and the
data in another mdb file.

The classic multi-user set-up is to have the data tables in a back end file
on a server and the front end file containing all other objects with linked
tables to your back end on each user's local drive.

How would that work with security delivered via an mdw file?

You would create both front and back end files whilst joined to your custom
workgroup. You would then be able to launch your app using a desktop
shortcut using the "wrkgrp" command line switch to specify the mdw file.

If you have a rummage around on this group there's a wealth of information
on all of this. Post back when you need more info.

Regards,
Keith.

 

[Bill]

It would reduce the risk of corruption.


The classic multi-user set-up is to have the data tables in a back end
file on a server and the front end file containing all other objects with
linked tables to your back end on each user's local drive.


You would create both front and back end files whilst joined to your
custom workgroup. You would then be able to launch your app using a
desktop shortcut using the "wrkgrp" command line switch to specify the mdw
file.

If you have a rummage around on this group there's a wealth of information
on all of this. Post back when you need more info.

Regards,
Keith.

Keith,
Many thanks for the advice.
Regards.
Bill.