Upgrading to SQL Server

I am converting a long working Access project to SQL Server

The problem is that it is riddled with DAO Commands and also the DAO Data Control

Most DAO commands can be converted to ADO resonably easily, except for FIND, FIND NEXT, SEEK of which I have a quite few.

There are quite a few forms which use the DAO Data Control

My instincts tell me to abandon the use of Data Controls (Even though I could use the ADO Data Control in place of the DAO Data Control) and simply use SQL Commands, which is going to treble the amount of work to do the conversion

Any comments appreciated

Use the data form wizard with the option of ado code or class to make your forms really quick and then customize them from there.

Good Luck

Re-write in VB.Net while you're at it. Too hard to convert old forms.

Where can I find this please ?

Quote:

---

data form wizard with the option of ado code or class

---

I've got 185 Forms in one main project, and about 30 more projects with an average of 10 forms each - All together make up my ERP solution

I have about 60% of the project already written using ADO SQL Data Access which I started to do in anticipation of upgrading to SQL Server one day

Might CREATE forms, but I don't think anything will convert them...

Just wondering about using an ADO Class to keep code managable

Never use those databound controls, just use pure ADO code, it will save you a lot of headaches later on.

Quote:

---

Originally Posted by George1111

Just wondering about using an ADO Class to keep code managable

---

If you are looking at converting Access to SQL, you should be aware that you can't have Forms, etc in SQL Server. As dglienna already suggested, you should most probably re-write the User interface part of your access DB in .NET. This way you would take advantage of what ,NET has in store for you and your database would be separated from your presentation.

Apart from that having SQL as a back-end would require a front-end application that will communicate with the SQL Database. I have never seen Access Forms being exported to some other format.

Quote:

---

Originally Posted by George1111

Where can I find this please ?



I've got 185 Forms in one main project, and about 30 more projects with an average of 10 forms each - All together make up my ERP solution

I have about 60% of the project already written using ADO SQL Data Access which I started to do in anticipation of upgrading to SQL Server one day

---

Just for test purposes start a new standard exe project.
In VB's IDE, goto VB's menu Add-Ins>Add-In Manager, select/highlight VB 6 Data Form Wizard. Then in the lower right corner where the frame has the caption of "Load Behavior", select Loaded/Unloaded so that there is a check in the box, then click ok.

GoTo Add-ins>Data Form Wizard, and follow it step by step but make sure you select code in the right place. (Actually I would suggest that you use every possible combination of control, code, and class in combination with the display/form types and save this test project as a reference.)

Good Luck

Thanks vb5prgrmr, thats worked out nicely !