J
JohnLute
I have a small, secured application that's split into FE and BE files with
the BE placed on a server for global access over a WAN (I can hear your
groans).
Be that as it may (reality can be ugly) I need help understanding an error
I'm getting which is 2105.
The FE is saved to local machines. The FE links to the BE. From my PC I
login as a full data user and experience no problems. Several others can also
run it without problems, however several others get the 2105 error.
Today I logged onto one of our "problem" PC's and then opened the database
with no issues. Great! I logged off the PC and the owner of it logged on and
tried to run the database. Guess what? 2105!
This doesn't make sense. He used the SAME database login that I used.
Has anyone run into this before?
Thanks!
the BE placed on a server for global access over a WAN (I can hear your
groans).
Be that as it may (reality can be ugly) I need help understanding an error
I'm getting which is 2105.
The FE is saved to local machines. The FE links to the BE. From my PC I
login as a full data user and experience no problems. Several others can also
run it without problems, however several others get the 2105 error.
Today I logged onto one of our "problem" PC's and then opened the database
with no issues. Great! I logged off the PC and the owner of it logged on and
tried to run the database. Guess what? 2105!
This doesn't make sense. He used the SAME database login that I used.
Has anyone run into this before?
Thanks!