SQL Server 2000 To Access 2000

Results 1 to 2 of 2

Thread: SQL Server 2000 To Access 2000

  1. #1
    Join Date
    Dec 1969

    Default SQL Server 2000 To Access 2000

    Hello.<BR><BR>I wrote a data-tier file that works with SQL Server 2000. It does regular stuff like connecting to the database, calling stored procedures, etc.<BR><BR>Now I wrote it with SQL Server 2000 in mind, but now I just got a project that is going to use Access 2000. My question is that how much of my data-tier file do I have to change.<BR><BR>I read somewhere that all i have to change is the connection string i.e. from<BR><BR>"Provider=SQLOLEDB;Data Source=xxxx.xxxx.xxx;Initial Catalog=xxxx;User ID=xxxx;Password=xxxx;"<BR><BR>to<BR><BR>"Provider =Microsoft Access Driver (*.mdb);Data Source=xxxx.xxxx.xxx;Initial Catalog=xxxx;User ID=xxxx;Password=xxxx;" (or something similar)<BR>

  2. #2
    Join Date
    Dec 1969

    Default RE: SQL Server 2000 To Access 2000

    There are some other differences, for example Access uses # ase a datedelimiter and SQL Server &#039;.<BR><BR>This has been asked before, if you do a search in this forum you&#039;ll find some posts.<BR><BR>Have you ever considered MSDE (it&#039;s &#039;desktop&#039; version of SQL Server). <BR>In certain cases you are allowed to redistribute this. MSDE works exactly the same as SQL Server (same engine) but has a limit of 5 concurrent workload batches and 2GB.<BR><BR>Check the microsoft site.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts