Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Westi on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

A2000 on XP machine funcionality problem 2

Status
Not open for further replies.

dabruins

Programmer
Mar 9, 2005
102
CA
I don't expect a complete answer to my problem but am hoping to find a good site(s) that desribes the effects of the OS, Database client and database version on the functionality on the database interface provided to the user. The more help anyone can provide will be most appreciated though!

I have an Access 2000 database being used by A2002 and A2003 clients on both Windows 2000 and XP systems. Those using the database from the Windows 2000 stations have no problems using the database interface as it has been developed in VBA, however the user of the DB on the XP workstations are experiencing problems with some of the developed functionality.

A preliminary diagnosis is that the binary operators utilized in some of the query statements WHERE clauses are not being recognized? (Ex. "SELECT TIME.hours WHERE TIME.dt = #01/11/2005#;" will work just fine while "SELECT TIME.hours WHERE TIME.dt >= #01/11/2005# AND TIME.dt <= #30/11/2005#;" results in the entire TIME table being returned.

I'm also experiencing problems with report generation. The default settings of the report (page size) seems to get thrown out when opened by the XP user.

Again I would appreciate any information helping me to understand how all these different versions of software and databases work together in access.

 
Hi.

With respect to report settings, take a look within the accass app, under Toos ---> Options, under the General Tab, unselect Track Name AutoCorrect. That usually fixes that problem.

Regarding your Select, the #01/1/2005# is Month, Day, Year, while #30/11/2005# appears Day, Month, Year.

Is there a chance that this is the cause? If so, a date setting on one machine that makes it work?

ChaZ

There Are 10 Types Of People In The world:
Those That Understand BINARY And Those That Don’t.
 
No ChaZ, the same Select query works on other client systems so the date format given isn't the problem. I've also tried using different formats to be sure and it didn't help. I have a user on an XP system using A2003 and things seems to work just fine. I'm convinced it is a problem of compatability with XP Pro and A2002. Again I'm having trouble finding information on what to look and test for? I don't think it would be as simple as changing settings in ACCESS? I'll look into the reports setting changed you noted here though and see if that works.

Thanks!
 
Anyway, why not always use NON AMBIGUOUS date format ?
Between #2005-11-01# And #2005-11-30#

Hope This Helps, PH.
Want to get great answers to your Tek-Tips questions? Have a look at FAQ219-2884 or FAQ181-2886
 
Without reading the entire thread ..
did you check the date & time format in the regional settings? are they same in both machine?

________________________________________________________
Zameer Abdulla
Help to find Missing people
Do not cut down the tree that gives you shade.
 
Thanks Zameer and PH. I'll check both options and see how it works.

Thanks.
 
Ahhh! Someone's always gotta be different. Thanks Zameer! That took care of all the problems we were experiencing. Though somewhat embarrassed by my lack of knowledge I'm happy to find its nothing more complex than changing a single setting.

Thanks to you all for your help!
 
But don't forget to take care of PHV's suggestion. You can't force all users to set their regional setting to your wish. Then they must be complaining another app is not working.

________________________________________________________
Zameer Abdulla
Help to find Missing people
Do not cut down the tree that gives you shade.
 
Yes your absolutely right. How does one check the current user regional settings in VBA to format the query string appropriately? This sort of thing is going to be popping up all the time so I'd better learn how to code for it now.
 
Seems you didn't understood my advice:
use non ambiguous date format in your code and don't worry the regional setting !

Hope This Helps, PH.
Want to get great answers to your Tek-Tips questions? Have a look at FAQ219-2884 or FAQ181-2886
 
So Format(dteBeginningDate,"yyyy-mm-dd") before passing the beginning and end dates into to the query string? I'm not sure why this is referred to as a Non-ambigous format though?
 
I'm not sure why this is referred to as a Non-ambigous format
This ANSI-like format clearly states where are the month and the day values ...

Hope This Helps, PH.
Want to get great answers to your Tek-Tips questions? Have a look at FAQ219-2884 or FAQ181-2886
 
Great. I'll stick to that from now on. Thanks again PHV!
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top