ADO.NET sql server to access

[anat2403]

If a project is written in ASP.NET with database in sql server and we want to create the same project with database in access, are there many changes in the code beside the connection string?

[PlausiblyDamp]

It really depends on how you are accessing the SQL server - if you are using stored procs (and you probably should) then depending on your version of access these may not be supported at all.

Also the way OleDb and Sql handle parametrised queries (you should be using these as well) is different and will need to be changed.

 

Without seeing any examples of your DB or .Net code though it is very difficult for anyone to offer any specific advice.

Edited March 4, 2007 by PlausiblyDamp

[TheWizardofInt]

If a project is written in ASP.NET with database in sql server and we want to create the same project with database in access' date=' are there many changes in the code beside the connection string?[/quote']

 

Your SQL statements will be different for your inserts and your searches

[kejpa]

But... Why?

If you want a copy for test/development you can use the same sql-server, just use another db in the same server. Or you can use a free version of sql server on your development computer.

If it's a production web project you better not use access since it's not intended to be used with multiple users.

 

Regards

/Kejpa

[TheWizardofInt]

But... Why?

If you want a copy for test/development you can use the same sql-server, just use another db in the same server. Or you can use a free version of sql server on your development computer.

If it's a production web project you better not use access since it's not intended to be used with multiple users.

 

Regards

/Kejpa

 

You will find that all of the different sequential query language programs use different commands in their queries

 

For example, you can't use 'Top' in MySQL

 

The big thing that I have found in Access is that it handles date values differently, so you have to run two different types of queries to search for date.

[Nerseus]

The main reason I see to want to move from SQL Server to Access if for portability. For example, to put your whole webserver on a laptop to take around and showoff (for product demos).

 

I would strongly suggest using MSDE in place of SQL Server for something like that. It's a bit harder to setup, but mimics SQL Server in every regard (it isn't LIKE SQL Server, it IS SQL Server) except number of connections. It would be a painless switch whereas going to Access is likely to NOT go smoothly.

 

-ner

[TheWizardofInt]

Have you all put any truth to the rumor that MS is dropping Access in favor of MSDE anyway?

 

I was hearing that it is was a definate, then at Vegas they were touting how many people use it and how great it is

[FZelle]

First of all, MSDE is dead, there is now the MS-Sqlserver Express.

 

Secondly, there is now article on a MS site that states anything near an end of access.