|
Home > Archive > MS SQL Server ODBC > October 2006 > Re: Access 97 to SQL Conversion
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Re: Access 97 to SQL Conversion
|
|
| Rick Vooys 2006-10-24, 6:40 pm |
| I am experiencing the same issues with SQL Server 2005 and Access 97. I don't
think it is cost effective for us to convert to Access 2003 because we would
have to purchase 12+ liscenses and we are re-writing the app in ASP.Net after
we get the backends converted and stable.
So ... is there any workarounds for this incompatibilities? What are they in
more detail, I am just testing and finding the same issues Dianne is having
(certain forms will not allow edits, some DOA recordsets will not not add
records?).
Thanks ahead of time, Rick
"Mary Chipman [MSFT]" wrote:
> Is your front-end Access 97? If so, then you'll solve a lot of your
> problems by upgrading to Access 2003. Access 97 is no longer
> supported, and never worked smoothly with SQLS 2000, mostly due to
> data type incompatibilities.
>
> --Mary
>
> On Fri, 20 May 2005 11:49:37 -0700, Dianne
> <Dianne@discussions.microsoft.com> wrote:
>
>
>
| |
| Sue Hoegemeier 2006-10-24, 6:40 pm |
| From a SQL Server perspective, you can TRY running the SQL
Server 2005 user database is a lower compatibility mode but
if you are using a front end that's no longer supported, it
would probably just minimize some of the issues - if even
that.
But you'd probably find more information on working around
the Access 97 issues in one of the Microsoft Access
newsgroups.
-Sue
On Fri, 29 Sep 2006 14:12:01 -0700, Rick Vooys
< RickVooys@discussion
s.microsoft.com> wrote:
[color=darkred]
>I am experiencing the same issues with SQL Server 2005 and Access 97. I don't
>think it is cost effective for us to convert to Access 2003 because we would
>have to purchase 12+ liscenses and we are re-writing the app in ASP.Net after
>we get the backends converted and stable.
>
>So ... is there any workarounds for this incompatibilities? What are they in
>more detail, I am just testing and finding the same issues Dianne is having
>(certain forms will not allow edits, some DOA recordsets will not not add
>records?).
>
>Thanks ahead of time, Rick
>
>"Mary Chipman [MSFT]" wrote:
>
| |
| Rick Vooys 2006-10-24, 6:40 pm |
| Thanks Sue. Can you elaborate on the lower capability mode? What would we
lose? Is this something you can just switch on and off? How would one go into
one of these modes?
"Sue Hoegemeier" wrote:
> From a SQL Server perspective, you can TRY running the SQL
> Server 2005 user database is a lower compatibility mode but
> if you are using a front end that's no longer supported, it
> would probably just minimize some of the issues - if even
> that.
> But you'd probably find more information on working around
> the Access 97 issues in one of the Microsoft Access
> newsgroups.
>
> -Sue
>
> On Fri, 29 Sep 2006 14:12:01 -0700, Rick Vooys
> < RickVooys@discussion
s.microsoft.com> wrote:
>
>
>
| |
| Sue Hoegemeier 2006-10-24, 6:40 pm |
| You'd loose the functionality introduced in the higher
version. You can change between different compatibility
levels and change back to 9.0. To do so, you would executed
sp_dbcmptlevel. You can find a lot of information on this
system stored procedure and the behavioral, functional
differences in books online under sp_dbcmptlevel.
-Sue
On Mon, 2 Oct 2006 09:53:02 -0700, Rick Vooys
< RickVooys@discussion
s.microsoft.com> wrote:
[color=darkred]
>Thanks Sue. Can you elaborate on the lower capability mode? What would we
>lose? Is this something you can just switch on and off? How would one go into
>one of these modes?
>
>"Sue Hoegemeier" wrote:
>
|
|
|
|
|