2000 project + backend upgraded to 2005 = issue!

  • Thread starter Thread starter IMK
  • Start date Start date
I

IMK

Hello all,

I have an Access 2000 project that had been connected to a SQL Server
2000 backend and worked beautifully for years. Recently we upgraded
our database server to SQL 2005 and I got a few hiccups.

The ORDER BY statements on the views I use in the application no
longer seem to work within the project. They sort fine on the back
end, but in the project they don't sort and, well, that's it really,
but there are a lot of records in these views so my users are starting
to get cross with me.

I can't seem to find an obvious fix. I'm guessing that I may need to
get these guys a newer version of access to run project in. If so,
what version should I get.

Keep in mind that I usually compile my projects and run them within
the Access 2000 runtime on my user's computers. What is the state of
the runtimes in newer versions of Access?

Thanks in advance.
 
Order By (probably associated with a TOP 100 percent in your case) in a View
is an unsupported sql-statement that have been removed from SQL-Server 2005.
Either add a TOP 2000000 to your Views (not sure about this one) or add an
Order By statement somewhere else than in the views or go back to SQL-2000.
(BTW, why did you upgrade to SQL-2005 if everything was working fine on
SQL-2000?)
 
Thanks, I did mess a bit with the SQL statements and everything seems
to be working now.

As for the upgrade, well, I work at governmental agency that had a big
pile of money that they needed to spend or lose.I didn't have much say
in the matter.It embarrasses me to say it, but an awful lot of
upgrading goes on here for that reason. Oh, and yes, I had things
running quite smoothly prior to the upgrade. Go figure.
 
Back
Top