Re: Access 2003 and SQL Server 2005 Express

On 26 Jun 2006 13:54:48 -0700, jmnaste@xxxxxxxxxxx wrote:

Worked fine for me when I just tried (using the Northwind sample db),
so I don't think it's an inherent problem with Access 2003.
Are you on the latest service packs for Office and SQL Server 2005?
My instance is called <machinename>\SQLEXPRESS. Did you specify the
correct instance name?

-Tom.



Hi,

I tried to migrate data of an Access 2003 application (.mdb) to SQL
Server 2005 Express.
Using the Wizard and choosing 'create a new database', I receive (a
French message saying roughly) '... migration wizard requires SQL
Server version 6.5 sp 5 and later ... connect to an SQL server source
of data.'.

Given that failure, I went to another PC running MSDE (according to
readme file it should be SQL server 2000 service pack 3). Started
migration and it worked just fine. Did some tests and this is really
what we need.

My conclusion has been that Access 2003 has trouble connecting to SQL
Server 2005. Trying to find an answer browsing posted messages, it
sounds like both should connect. Is it just the method I am using that
don't work? The message says that 'the wizard' is not compatible,
is there another way?

I went back to the machine with SQL 2005 and created a small DB using
SQL Client. I started the wizard and this time using the 'use an
existing DB' option but in the end I received the same message.

Is Access 2003 compatible with SQL Server 2005 Express and if so, I
think I need some help about how to do it.

Thank you.

.

Relevant Pages

  • Re: How to import one DB to another using any tool
    ... I'm simply looking for an easy GUI way of doing this. ... If you absolutely want a wizard, there is the Copy Database Wizard ... Keep in mind that when working with a server application like SQL ... Erland Sommarskog, SQL Server MVP, esquel@xxxxxxxxxxxxx ...
    (microsoft.public.sqlserver.programming)
  • Re: Access 2007->SQL Server2005 "connection was forcibly closed",G
    ... I moved every table I was able to move to the SQL ... closed connections - but all of these errors are in the version which used ... the SQL Server 2000 and everything worked ... communication between ODBC (OLEDB and Native Client, ...
    (microsoft.public.sqlserver.connect)
  • It can be Done
    ... I just installed a 3 SQL Server 2005 instances on a 2 node Active/Passive cluster. ... IWiz will then offer you a choice of Group on where you can install teh Fail Over Clustered Instance of SQL. ...
    (microsoft.public.sqlserver.clustering)
  • Re: Unable to Apply SP4 to SQL 2000 Cluster (new Node)
    ... Rebuild the node in the failover cluster. ... Scenario 1" in SQL Server 2000 Books Online. ... This setup process updates to SP4 only the binaries on the new ...
    (microsoft.public.sqlserver.clustering)
  • Re: WSS 3.0 question
    ... I followed the advise given in removing WSS 3.0 etc, ... the server is complaining that the SQL service(?) was tempered with or corrupt. ... I may just instal the SQL server as I was going eventuall use it anyway. ... If WSUS 3.0 is installed, I would suggest you uninstall it and then you install WSS 3.0. ...
    (microsoft.public.windows.server.sbs)