Access 2003 and SQL Server 2005

A

Aljosa

Hi!

I have developed an application in Access which uses Access database. Now I
need more powerfull database. I would like to convert my application to
Access project and use SQL 2005 database.
What do you think about that combination? After some testing I noticed that
Access 2003 does not support SQL 2005.

Thank you all for any information!
 
O

Ofer

I have an access application with sql server, we have around 60 users, it's a
work flow application, we have no problem and its works perfectly for the
last 7 Years.
We moved From Access2.0 to Access 97 and now Access 2003.

The havy procedures and queries we developed in the sql
Queries - as views or pass through queries in Access.
Functions - as Stored procedures in the SQL server

I didn't hear about a problem between Access 2003 and SQL 2005, but mybe
somebody else can replay for this question.

I'm very happy with the combination batween Access and SQL Server
 
A

Aljosa

There are up to 30 users at the same time and every day more and more data.
If the final version of SQL 2005 isnt out yet I can also use beta version or
SQL Express until it comes out.
I just need to know what problems can I expect with Access 2003 and SQL
Server 2005 together. It will be a lot of work to convert Access application
to Access project application and I dont want to throw one month of work away
to see that SQL 2005 realy doesnt work well with Access. Then I will have to
use previous version of SQL server (and buy the licenses for the rest of 25
users).

Thank you all for any information!
 
C

Craig Alexander Morrison

You should stick with SQLS2000 (if indeed Jet 4 would not suffice) as
SQLS2005 would have to run in 2000 compatibility mode to work with Access,
therefore not worth the hassle of SQLS2005.

Also SQLS2000 is tried and tested, no need to use the "latest" toy with a
production database unless the toy gives you something very useful.

If you are using any version of Access SQLS2005 is not for you. The
"features" that have been added to SQLS2005 are mainly for developers using
tools other than Access.

I would not recommend the use of ADPs especially if you are converting from
a working MDB solution.
 
A

Aljosa

The reason why I am thinking about SQL 2005 instead of SQL 2000 is that SQL
2005 Express is not limited to 5 users. My application is installed in many
locations with many users. This means huge costs for all locations to buy SQL
2000 and additional licenses.
 
C

Craig Alexander Morrison

Consider using Terminal Services, SQLS2005 is new - is it reliable?
Microsoft do not have a good reputation on getting new things right first
time, Access 95, Access 2000.

SQLS2000 Desktop is not limited to 5 users it is "throttled" after 5
concurrent Transact-SQL batches it can support many more users performing
data entry tasks quite well.

If you insist on using SQLS2005 remember 2000 compatibility mode.

You may find that Terminal Services and Jet 4 is more than adequate for your
purposes.
 
Top