Hi Gang,

I have a potential client with the following needs:

Create a custom .NET invoicing program (entry/edit/printing, etc.) that will send summary batch information to their existing accounting system. Sounds like gravy, but you know there just has to be a hair in that gravy: the accounting system backend is Pervasive.SQL (good ole [read old] BTrieve). I can use MSDE for the backend of the .NET program where my custom detailed invoices will reside, but I have to pull out of and update the Pervasive.SQL side with summary invoice data as well as the last used invoice numbers, customer information, etc.

I know the accounting system currently relies upon ODBC connections to the Pervasive.SQL databases. I have used some utilities and can usually only see the data in hex format from the tables.

So here is the issue: if we tell them it will be a major number of hours to accomplish the connection/updates to Pervasive.SQL, they just might convert the backend over to MS-SQL (an easy procedure) and we will all live happily ever after.

So anyone ever had to fight with Pervasive.SQL, and if so, who won ???

TIA !!!

Best Regards,
Jace