Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations IamaSherpa on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Pervasive/Btrieve to MSSQL, Macola 7.6.400b 1

Status
Not open for further replies.

joybee36

Technical User
Feb 10, 2006
29
US
We are planning an migration to mssql, and have some third party applications that access our Macola databases. I am assuming that the actual table structure isn't going to change with this migration, but my programmer has the following questions, can anyone help?

Will the SQL server database tables be organized, named, and formatted the same.

Will these tables have the exact same set of columns?

If not, what are the new columns and how are the populated.

Thanks!
 
For the most part, the answer is yes. A few exceptions:

EDI
Payroll
OEPRCFIL - OE Price Codes File
SYCDEFIL - System Codes File

In the case of the last 2, in Pervasive, these were broken out into several logical views in the .ddfs, whereas they are just one table in SQL.

If you have crystal reports or other applications looking at these 2 tables, you will need to revisit these apps.

If you use F9, Star Ship, or other 3rd party applications, you may have to upgrade them as well. What 3rd party apps are you currently using?

Software Sales, Training, Implementation and Support for Macola, eSynergy, and Crystal Reports

"If you have a big enough dictionary, just about everything is a word"
--Dave Barry
 
The program that we are most concerned about was written by a private programmer as a way to "dump" orders received via ftp site into the order entry and accounts receivable tables, not something out of the box. We also use Shipgear and MacWeb, but I think we have them buttoned down. If those are the only changes that are made to the tables, however, I don't think we'll have any problems. Thanks for your help!
 
Provided that you have the source code for the program in question, it should not be too hard to modify it to point to the SQL database.

All your crystal reports will need to be pointed to a new ODBC DSN, but there is a tool to help you to do this - Report Inspector. Check out


Software Sales, Training, Implementation and Support for Macola, eSynergy, and Crystal Reports

"If you have a big enough dictionary, just about everything is a word"
--Dave Barry
 
Don is correct as long as you were using the _SQL portion of the DDF. If not there are many changes to the names of the fields frro the non _SQL vs the _SQL, but the physical position of the data is relativly the same.

Steve Henley
Trianglepartners.com
Exact Software consulting, sales and implementations.

If the only tool you can use is a hammer then all your problems look like nails.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top