G
General Fear
I have not found much information on the net that discusses unbound
forms.
I wanted to go the unbound route because I will have many concurrent
users. What I want to do is split the MDB in 2. The data will be on an
MDB on the server. The front end will be local on the end user's C
Drive.
To give you an idea at what I am doing, the local front end MDB that
is on the C Drive will retrieve a single record. Say, where customer
ID equals 123 returning just one record. The user changes the record
locally then sends it back to the server MDB.
In order to do this I have to manage concurrency in a multi user
setting. I have done this in the past with other software. But before
I go down this road in Access, I wanted to read more about this and
take advantage of the wisdom that is out there before I try it.
So folks. Any suggestions? Any help will be greatly appreciated.
Regards.
forms.
I wanted to go the unbound route because I will have many concurrent
users. What I want to do is split the MDB in 2. The data will be on an
MDB on the server. The front end will be local on the end user's C
Drive.
To give you an idea at what I am doing, the local front end MDB that
is on the C Drive will retrieve a single record. Say, where customer
ID equals 123 returning just one record. The user changes the record
locally then sends it back to the server MDB.
In order to do this I have to manage concurrency in a multi user
setting. I have done this in the past with other software. But before
I go down this road in Access, I wanted to read more about this and
take advantage of the wisdom that is out there before I try it.
So folks. Any suggestions? Any help will be greatly appreciated.
Regards.