Just a quick check to see if anyone has also encountered this bizarre quirk:
Access97, front end .mde files to back end .mdb file
After working fine for a few years, a form in the front end .mde file started having the problem below.
In a subform, set up as continous forms with one field bound to a combo box, whose datasource is a query WHERE'd to a value in the main form.
(The field is a production run ID and the datasource presents a list of all possible run IDs for the Part contained in a textbox on the main form.)
If more than one user opens the front end (all users share the same front end, it isn't distributed as separate copies to each user), the combo box displays all Run IDs for all parts, not just the one it is supposed to. So I've had to make a second copy of the front end .mde file for the one user who uses this form, so that it will work the way it used to, even when other users launched the same file.
I haven't gotten too detailed, because I'm not at work now, but am wondering if anyone has any ideas why multiple launches of an .mde front end would cause combo box datasource query to stop applying the WHERE filter?
TIA
Access97, front end .mde files to back end .mdb file
After working fine for a few years, a form in the front end .mde file started having the problem below.
In a subform, set up as continous forms with one field bound to a combo box, whose datasource is a query WHERE'd to a value in the main form.
(The field is a production run ID and the datasource presents a list of all possible run IDs for the Part contained in a textbox on the main form.)
If more than one user opens the front end (all users share the same front end, it isn't distributed as separate copies to each user), the combo box displays all Run IDs for all parts, not just the one it is supposed to. So I've had to make a second copy of the front end .mde file for the one user who uses this form, so that it will work the way it used to, even when other users launched the same file.
I haven't gotten too detailed, because I'm not at work now, but am wondering if anyone has any ideas why multiple launches of an .mde front end would cause combo box datasource query to stop applying the WHERE filter?
TIA
