DAO to ADO covertion 1

[MALICKA]

Inventory project using access & vb(DAO) now i need to change to sql server
So how to change dao to ado
how to deal with workspaces in dao when change to ado

 

[jgpasko]

Malicka,

You don't necessarily have to convert over to ADO. MS SQL Server is backward compatible with DAO. It is recommended that you eventually migrate to ADO, but you can perform this in stages. The big issue will if you want to leverage SQL Server's full power and convert some of your business rules that might be reside on the Client side into stored procedures so that the server does more of the work.

http://msdn.microsoft.com/library/en-us/dndao/html/daotoadoupdate.asp

This link provides guidance on process and issues for DAO to ADO migration.

Good Luck John Pasko
john@rts-sd.com
"No matter where you go, there you are."

 

[CCLINT]

Huh?

At this point, the best thing you can probably do is use a front end MDB with linked tables to the Server until you have time to make all of the changes.



[/b][/i][/u]_{*******************************************************
General remarks:
If this post contains any suggestions for the use or distribution of code, components or files of any sort, it is still your responsibility to assure that you have the proper license and distribution rights to do so!}

 

[jgpasko]

CCLINT,

It looks like the Client is already in place (Using VB) with an access mdb as the backend. Malicka has to upsize to SQL Server. Why rewrite it as an mdb when the Client code, forms etc is already in VB? This is what I gathered from the limited scope of info provided.

John Pasko
john@rts-sd.com
"No matter where you go, there you are."

 

[CCLINT]

For now, MALICKA would only need to link to tables in SQL Server via front end MDB instead of using actual tables in the MDB. That will give MALICKA some time to make the change, while still being able to use the SQL tables on a limited basis, with-out having to change much of the specific sql syntax. [/b][/i][/u]_{*******************************************************
General remarks:
If this post contains any suggestions for the use or distribution of code, components or files of any sort, it is still your responsibility to assure that you have the proper license and distribution rights to do so!}

 

[CCLINT]

What I'm saying, is to just deleted the tables in the MDB, and create links to the SQL tables in the MDB.
Nothing about writing any code or forms in an MDB. The VB remains the client.
[/b][/i][/u]_{*******************************************************
General remarks:
If this post contains any suggestions for the use or distribution of code, components or files of any sort, it is still your responsibility to assure that you have the proper license and distribution rights to do so!}

 

[MALICKA]

Hi Thanks all
What i need is to access vb through sql server
I already transfered the mdb files to sql server & made the
Connection in vb to connect to sql server but still
I could not access the data

MR CCLINT how is possible to access sql server without modifying the code in VB

& the inventory is working fine with access now i have to trasfer to sql server So its an upgrade .

I was informed Ado is more reliable for sql server & may until i convert i can go with DAO
if so how to connect to it I already made the connetion
& can get connected but can't access any table to i need to change the record set

Regards
-M

 

[MALICKA]

Tks jg
msdn link was very usful to convert from dao to ado
Now i have problem on seek
in dao its
rs.Seek "=", Trim(cKeyValue)
i change in ado as below it gives error
rs.Seek Trim(cKeyValue)