Hi

Has anyone out there had any problems running Win2k (SP4)
workstations/Access 2003/SqlServer 2005 in combination?

I have a client reporting connection dropout when loading our shrink-wrapped
Access ADE app, preceded by an error message saying 'class not registered'.

Not sure if this is an Access problem, or a Win2k problem run against the
SQL Server...

Any relevant comments gratefully received

TIA

Steve

I have an app deployed in that architecture, although mine is an adp. I
haven't had any problems like that.

Barry

"CyberDwarf" wrote:

> Hi
>
> Has anyone out there had any problems running Win2k (SP4)
> workstations/Access 2003/SqlServer 2005 in combination?
>
> I have a client reporting connection dropout when loading our shrink-wrapped
> Access ADE app, preceded by an error message saying 'class not registered'.
>
> Not sure if this is an Access problem, or a Win2k problem run against the
> SQL Server...
>
> Any relevant comments gratefully received
>
> TIA
>
> Steve
>
>
>

As I understand, you can't use Access 2003 (or earlier) ADP/ADE against SQL
Server 2005. To use an ADP/ADE with 2005, you must use Access 2007.

Regards,
Graham R Seach
Microsoft Access MVP
Sydney, Australia
---------------------------

"CyberDwarf" <steve.ingle@lineone.net> wrote in message
news:uF0c%23hv4GHA.3396@TK2MSFTNGP05.phx.gbl...
> Hi
>
> Has anyone out there had any problems running Win2k (SP4)
> workstations/Access 2003/SqlServer 2005 in combination?
>
> I have a client reporting connection dropout when loading our
> shrink-wrapped Access ADE app, preceded by an error message saying 'class
> not registered'.
>
> Not sure if this is an Access problem, or a Win2k problem run against the
> SQL Server...
>
> Any relevant comments gratefully received
>
> TIA
>
> Steve
>

> As I understand, you can't use Access 2003 (or earlier) ADP/ADE
> against SQL Server 2005. To use an ADP/ADE with 2005, you must use
> Access 2007.

Absolutely not.

You CAN create ADPs with Access 2003, using SQL 2005 as back-end. I did it.
What you CANNOT do is manipulate SQL 2005 objects via Access 2003, because
SQL-DMO has significant changes from previous version.

--
PBsoft di Gabriele Bertolucci
www.pbsoft.it
skype: pbsoftsolution

PBSoft is correct. However, it sounds like MS is starting to steer people
away from ADP's. This page sums it up pretty well:
http://www.databaseadvisors.com/gazette/sqlexpress.htm

Barry

"CyberDwarf" wrote:

> Hi
>
> Has anyone out there had any problems running Win2k (SP4)
> workstations/Access 2003/SqlServer 2005 in combination?
>
> I have a client reporting connection dropout when loading our shrink-wrapped
> Access ADE app, preceded by an error message saying 'class not registered'.
>
> Not sure if this is an Access problem, or a Win2k problem run against the
> SQL Server...
>
> Any relevant comments gratefully received
>
> TIA
>
> Steve
>
>
>