RE: Moving from Jet to SQL Everywhere (compact edition)
- From: v-garych@xxxxxxxxxxxxxxxxxxxx ("Gary Chang[MSFT]")
- Date: Mon, 04 Dec 2006 07:04:46 GMT
Hi,
Is it just a matter of using a different connection string with
my ADO?
If your application uses the ADO to access the databse, you don't need
regenerate your program to adopt with the SQL Server, except for the target
SQL Server's database's structure is different from that Jet database.
Change the connection string would be OK.
Can I still use the current version of msado.dll - or do I need
to redo to a newer version?
We suggest you use the msado15.dll instead your the older version.
Are there differences in SQL that I need to worry about?
SQL Server database has much advance database feature that the Jet
database, if your application only use the feature of the Jet databse, I
don't think you need to worry about it. But it is better for you to perform
some tests.
Thanks!
Best regards,
Gary Chang
Microsoft Online Community Support
==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
ications.
Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscriptions/support/default.aspx.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
.
- Follow-Ups:
- Re: Moving from Jet to SQL Everywhere (compact edition)
- From: WishfulDoctor
- Re: Moving from Jet to SQL Everywhere (compact edition)
- References:
- Moving from Jet to SQL Everywhere (compact edition)
- From: WishfulDoctor
- Moving from Jet to SQL Everywhere (compact edition)
- Prev by Date: problem with dll function while inserting data
- Next by Date: Re: Moving from Jet to SQL Everywhere (compact edition)
- Previous by thread: Moving from Jet to SQL Everywhere (compact edition)
- Next by thread: Re: Moving from Jet to SQL Everywhere (compact edition)
- Index(es):
Relevant Pages
|
Loading