Wrox Programmer Forums

Need to download code?

View our list of code downloads.

Go Back   Wrox Programmer Forums > Microsoft Office > Access and Access VBA > Access
Password Reminder
Register
Register | FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read
Access Discussion of Microsoft Access database design and programming. See also the forums for Access ASP and Access VBA.
Welcome to the p2p.wrox.com Forums.

You are currently viewing the Access section of the Wrox Programmer to Programmer discussions. This is a community of tens of thousands of software programmers and website developers including Wrox book authors and readers. As a guest, you can read any forum posting. By joining today you can post your own programming questions, respond to other developers’ questions, and eliminate the ads that are displayed to guests. Registration is fast, simple and absolutely free .
DRM-free e-books 300x50
Reply
 
Thread Tools Search this Thread Display Modes
  #1 (permalink)  
Old October 7th, 2004, 08:20 AM
Authorized User
 
Join Date: Jul 2003
Location: Stockton on Tees, , United Kingdom.
Posts: 73
Thanks: 0
Thanked 0 Times in 0 Posts
Default Migrating from Jet to SQL

Hope the sages among you can help me.
We have quite complex Access databases that have grown over the years. They are generally split - front end and backend.
The code has been developed from Access 97, through to MS Access XP but based on Access 2000 file db format. Shortly to be upgraded to MS Access 2003 and sitting on a MS Server 2003. Coding is mainly Jet DAO with the odd ADO.
MS Access security is not implemented although there are multi-users attached.
The system is now creaking and we will be shortly upgrading to SQL, possibly to the recent announced MS SQL Express.
Sorry for the lengthy introduction but the nux of my query is:
"What is the best way for me to convert the existing systems?"
Any tips, references and experience would be very welcome.


Cheers Ray
__________________
Cheers Ray
Reply With Quote
  #2 (permalink)  
Old October 7th, 2004, 08:38 AM
Friend of Wrox
 
Join Date: Jun 2003
Location: Harrisburg, PA, USA.
Posts: 1,998
Thanks: 0
Thanked 3 Times in 3 Posts
Default

Hey,

It is extremely easy to import data from access to SQL Server using DTS. However, SQL Express doesn't have DTS. I can't remember if SQL Express has data import capabilities or not.

What do you mean by "odd ADO"? It's more common than DAO nowadays.

Brian
Reply With Quote
  #3 (permalink)  
Old October 8th, 2004, 04:43 AM
Authorized User
 
Join Date: Jul 2003
Location: Stockton on Tees, , United Kingdom.
Posts: 73
Thanks: 0
Thanked 0 Times in 0 Posts
Default

Thanks for the quick reply Brian.
By DAO I mean most of my references to datasets in the Dim statement are left open i.e. the dataset is not declared and therefore are defaulted as Variant and DAO datasets.
I know this is lazy but has served me well for years.
I get the impression that these would need converting to ADO and connections set up to SQL. This could be quite a lot of effort.
Still welcome further feedback from any of you.

Cheers Ray
Reply With Quote
Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off
Trackbacks are Off
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Migrating from SQL Express to Standard. how? saif44 SQL Server 2005 2 July 7th, 2006 08:02 PM
Migrating Access database to SQL Server lryckman SQL Server 2000 3 April 10th, 2005 02:19 PM
migrating from access to SQL morphy VB Databases Basics 1 December 10th, 2004 04:12 PM
Migrating SQL Server 7 to 2000 dg1234 SQL Server 2000 1 January 28th, 2004 02:22 PM
Migrating from access to sql server benjamintsmith Classic ASP Databases 0 July 31st, 2003 07:45 AM



All times are GMT -4. The time now is 07:50 AM.


Powered by vBulletin®
Copyright ©2000 - 2019, Jelsoft Enterprises Ltd.
© 2013 John Wiley & Sons, Inc.