Re: Access - ODBC to SQL - Incorrect Results
- From: lyle <lyle.fairfield@xxxxxxxxx>
- Date: Mon, 19 Nov 2007 18:24:24 -0800 (PST)
On Nov 19, 7:49 pm, Jensen.Ka...@xxxxxxxxx wrote:
My question was why 3 fields defined as the same thing in SQL server
holding the same format of data are acting differently in ACCESS.
This is one of those questions that is very difficult to answer
because it is so general, like "Why the sea is boiling hot" and
"Whether pigs have wings?"
Questions:
1. yyyy-mm-dd is 10 characters long. Why Varchar(20)?
2. Why yyyy-mm-dd rather than yyyymmdd? "-" has significance to many
search and filter engines beyond being a hyphen. It adds zip of
significance to yyyymmdd.
3. You say the data are in SQL server. You also say the data were
imported form SQL-Server. And you say, why won't what I want to
happen, happen in Access. Where are the data? And how are you
connecting? And what does in Access mean: on a form? in a recordset?
In the returns of a query? WHAT?
It sounds to me as if you are in too deep here. If you tell us some
specifics we might be able to help. I don't use ODBC but I've been
convinced of its effectiveness. It should be able to take your Access
commands and translate them into MS SQL-Server SQL that will give you
the results you need.
BTW. X-Base programs translated dates to yyyymmdd for sorting purposes
for years and years and years with no problems. Probably they still
do. So there should be no unsolvable problem in your using this
format. But I would create another date column and cast the yyyymmdd
strings to dates and use that. Why use a 13.5 compression ratio V-12
and give it regular gas ... or sub-regular gas?
.
- References:
- Access - ODBC to SQL - Incorrect Results
- From: Jensen . Katie
- Re: Access - ODBC to SQL - Incorrect Results
- From: Rich P
- Re: Access - ODBC to SQL - Incorrect Results
- From: Jensen . Katie
- Access - ODBC to SQL - Incorrect Results
- Prev by Date: Re: Detect Idle Time
- Next by Date: Re: Detect Idle Time
- Previous by thread: Re: Access - ODBC to SQL - Incorrect Results
- Next by thread: slow access using access 2007 on client/server
- Index(es):
Relevant Pages
|
Loading