I need to keep employee initials locked in front end application

[Guest]

I have a front to back split db from the switch board you select your
initials and login, which opens the data entry page with employee initials at
the top of the page. The initials field is bound to the switch board that
does not close. This is a 4 person multiuser db and when one person logs off
their initials move to another users interface. How can I stop this. I have
tried locking the initials field on the interface page but still it appears
to happen. One issue I have considered is that two of us that are not having
problems are using access 2003 and the two others are using 2000. Are there
any other locks that should be applied or change the way we login? I am
stummped

 

[Gina Whipp]

The way it sounds to me, it's as if they are all using the same Switchboard,
if they are then you need to need to change that, each should have a
front-end loaded on their own machine and that would avoid that problem.

HTH,
Gina Whipp

 

[Guest]

Gina,

Each user has their own front end loaded on their own machine, which is what
is bafling me

 

[Gina Whipp]

When they log-on, it is stored in any common table or in an unbound text box
on the the Switchboard?

And what is the interface page?

They way I do it is the frmLogOn which goes invisible after the user logs on
and there ID is transferred to the Switchboard after they Log-On, how does
yours work exactly?

Gina Whipp

 

[Guest]

The Switch board drop down is bound to the employee table, the initials on
the main form are bound to the main table

 

[Gina Whipp]

Okay, so the initials in both places are bound to a table. I don't remember
why and maybe someone can help with this (hopefully one of those gurus out
there) but my LogOn ID is stored in and unbound field on and invisible
log-on form and only closes when the user exits.

I THINK it has something to do with the tables are all drawing from the back
end and being stored in that field when a new user logs on the field in that
table changes causes the field on another users station to change. Binding
it an unbound text bos that holds the users log-on and does not look at the
table to see if any other user has changed those initials by logging on.
Hope that makes sense.

Gina Whipp

 

[Guest]

Thanks Gina !

Okay, so the initials in both places are bound to a table. I don't remember
why and maybe someone can help with this (hopefully one of those gurus out
there) but my LogOn ID is stored in and unbound field on and invisible
log-on form and only closes when the user exits.

I THINK it has something to do with the tables are all drawing from the back
end and being stored in that field when a new user logs on the field in that
table changes causes the field on another users station to change. Binding
it an unbound text bos that holds the users log-on and does not look at the
table to see if any other user has changed those initials by logging on.
Hope that makes sense.

Gina Whipp

 

[Gina Whipp]

Just in case you are still reading this thread... (I learn soooooo much
here) apparently, Access 2000 has this bookmark bug that seems to jump when
certain events are fired. That might be why only the Access 2000 's are
affected.

Your most welcome...
Gina Whipp