|
|
|||||||||
|
|||||||||
|
|||||||||
| |
|||
| |||||||||
![]() |
|
|
«
Previous Thread
|
Next Thread
»
|
Thread Tools | Search this Thread | Display Modes |
|
#1
|
|||
|
|||
|
SELECT . . . ORDER BY - SQL 2000 vs. JET 4
I have 2 data sets, one in a SQL 2000 database, the other in a Jet 4.0
database. I am using ADO, and a select statement to extract an identically keyed subset with an ORDER BY for a field (part number). Initially, an extract is made from the SQL database to create the Jet database. The Jet database is updated, then I am using the Jet database to update the SQL database (with VB6). Fields, other than the part number are updated (like quantity). The order in which the "ORDER BY" clause returns the data is different in SQL 2000 vs. Jet 4.0, therefore I cannot "match" the data with equal db.MoveNext statements. (Note that I have simplified what is being done for this query). This change in ORDER BY for the Jet database is documented at: http://support.microsoft.com/default.aspx?scid=kb;en-us;q236952 Does anyone have any ideas, short of seperate SELECT statements, on how to make the ORDER BY statements work the same? (Note, seperate SELECT statment are not an option as I have simplified what is being done). I really do not care how the data is ordered, I just want consistancy. Frank |
|
#2
|
||||
|
||||
|
I'm not sure what exactly you mean, ORDER BY statements work the same across all DB's - you are only able to choose between ASC & DESC...unless of course you mean that the SQLServer DB is set to case/accent sensitivity. Regardless,I would think you would want to match the primary keys when updating the SQLServer DB... relying on the ordering would be prone to errors.
|
![]() |
| Viewing: Dev Articles Community Forums > Databases > Microsoft SQL Server > SELECT . . . ORDER BY - SQL 2000 vs. JET 4 |
| Thread Tools | Search this Thread |
| Display Modes | Rate This Thread |
|
|
|
|