Recordset Query not functioning properly

  • Thread starter Thread starter Sue
  • Start date Start date
S

Sue

My database is on a common drive as a client / server
system (app is in one application and database is in
another). I have 12 people accesses this database and of
the 12, 10 people are not having any issues BUT on 2
computers when they are searching in a combo box and they
type in a number (i.e. 5436) the system tells you that
this Order No is not in the list.....then does the drop
down box thing and it is listed right there. You can then
select the order and it populates the fields......... On
any other drop down boxes that don't require numbers (i.e.
the form number drop down box where you would enter
something like CS0011) this works find?

I'm using DAO for the queries and recordsets.......does
this make any sense to you. I have looked everywhere,
tried everything and feel baffled....

Any advice you can give me would be greatly
appreciated........
 
Sue said:
My database is on a common drive as a client / server
system (app is in one application and database is in
another). I have 12 people accesses this database and of
the 12, 10 people are not having any issues BUT on 2
computers when they are searching in a combo box and they
type in a number (i.e. 5436) the system tells you that
this Order No is not in the list.....then does the drop
down box thing and it is listed right there. You can then
select the order and it populates the fields......... On
any other drop down boxes that don't require numbers (i.e.
the form number drop down box where you would enter
something like CS0011) this works find?

I'm using DAO for the queries and recordsets.......does
this make any sense to you. I have looked everywhere,
tried everything and feel baffled....

Any advice you can give me would be greatly
appreciated........
Click to expand...

I can't explain exactly what's going on, but the fact that it's
happening only on a couple of PCs suggests the old reliable References
bug. Often when databases don't work on one particular machine, it's
because of a broken or missing reference. See if the steps outlined
here help:


http://members.rogers.com/douglas.j.steele/AccessReferenceErrors.html
 
Yes that was very helpful. Thanks a bunch!

-----Original Message-----


I can't explain exactly what's going on, but the fact that it's
happening only on a couple of PCs suggests the old reliable References
bug. Often when databases don't work on one particular machine, it's
because of a broken or missing reference. See if the steps outlined
here help:


http://members.rogers.com/douglas.j.steele/AccessReference Errors.html

--
Dirk Goldgar, MS Access MVP
www.datagnostics.com

(please reply to the newsgroup)


.
Click to expand...
 
Back
Top