J
Jason Gyetko
I'm working with an Access frontend against a MySQL backend . When I have
more than one user connect to the same access database (it's in a shared
folder), and run the same form, which accesses the same record, I'm getting
#Deleted for everyone except the last person who open the form.
The way the form is setup is I have a Combo Box to select a description,
then a subform returns all the records that pertain to that description.
The first user opens the form and selects the description, the subform gets
populated. Now when the second user opens the form and selects the same
description, their subform gets populated and the first users subform
displays #Deleted for all the records. Is this because of the way I have my
form setup (maybe recordset, lock, ???? options), any suggestions would be
greatly appreciated.
If I copy the frontend .mdb file to multiple locations, then have the users
run their own individual database (all .mdb are still accessing the same
MySQL backend DB), I don't experience this problem. I can use this as a
work-around, but if possible, would prefer not to. Thanks.
more than one user connect to the same access database (it's in a shared
folder), and run the same form, which accesses the same record, I'm getting
#Deleted for everyone except the last person who open the form.
The way the form is setup is I have a Combo Box to select a description,
then a subform returns all the records that pertain to that description.
The first user opens the form and selects the description, the subform gets
populated. Now when the second user opens the form and selects the same
description, their subform gets populated and the first users subform
displays #Deleted for all the records. Is this because of the way I have my
form setup (maybe recordset, lock, ???? options), any suggestions would be
greatly appreciated.
If I copy the frontend .mdb file to multiple locations, then have the users
run their own individual database (all .mdb are still accessing the same
MySQL backend DB), I don't experience this problem. I can use this as a
work-around, but if possible, would prefer not to. Thanks.