A
Alan Knipmeyer
Hi,
I am currently migrating from Windows 98 to Windows 2000 Server using
a higher-specification machine. One of the reasons for doing so is
that the old windows 98 machine hosted an important database, the
system itself didnt have the capacity for RAID5 mirrors/hotswap
disks/automated backups,etc, but the Access database itself worked
fine over a shared drive and several people accessing it at the same
time.
With a share and directory setup on a Win2K server in 'Workgroup' mode
and using the 'Guest' account to access shares, the shared resource
will mount on each client machine, and whilst multiple clients can
open the database, any updates are not stored (and the 'who is logged
in monitor only shows one user').
To me it looks like a file locking problem but would appreciate any
help regarding the matter. In the mean time I`ll keep prototyping on
my lab and return with the results (I hate unfinished newsnet posts !)
Regards,
Al Knipmeyer
I am currently migrating from Windows 98 to Windows 2000 Server using
a higher-specification machine. One of the reasons for doing so is
that the old windows 98 machine hosted an important database, the
system itself didnt have the capacity for RAID5 mirrors/hotswap
disks/automated backups,etc, but the Access database itself worked
fine over a shared drive and several people accessing it at the same
time.
With a share and directory setup on a Win2K server in 'Workgroup' mode
and using the 'Guest' account to access shares, the shared resource
will mount on each client machine, and whilst multiple clients can
open the database, any updates are not stored (and the 'who is logged
in monitor only shows one user').
To me it looks like a file locking problem but would appreciate any
help regarding the matter. In the mean time I`ll keep prototyping on
my lab and return with the results (I hate unfinished newsnet posts !)
Regards,
Al Knipmeyer