Scott, I haven't used MAS software, but in general, accounting software packages do not want to allow any other software to be able to change the data, except through any provided import/export features, or through custom programming. One reason is protection of the integrity of the financials. The other is profitability through getting you to pay for their custom modules if you need something more.
If MAS allows you to import transactions in some way, R:BASE may be able to generate the format necessary for import. I have done programs for QuickBooks and Peachtree that work that way. Sometimes this can be simple CSV files. In the case of QuickBooks, it has to be according to their proprietary formats, but those formats are documented in their own help files. Bill R. Scott Stanfield wrote: > Here is the response that I am getting from the MAS consultant: > > In reviewing the BEST forum for MAS the senior members have the > following comments “DO NOT use the Read/Write ODBC driver from ProvideX > with MAS. It WILL result in 100% data corruption 100% of the time.” and > “To clarify a little more.. as Best intended the ODBC to be read only, > there are some key bits of info missing from the data dictionary which > are necessary to do writes through the ODBC.. This is why you get data > corruption, and why you shouldn't attempt it....” > > So at first I was told the ODBC simply did not allow a write (read only) > now I'm being told that it will corrupt the data if R:Base writes to > their database. I think that I'm getting a line....... because they > don't want this to happen. Does anyone know if R:Base would corrupt an > ODBC compliant ProvideX database? > > > > > At 03:36 PM 8/29/2005, you wrote: > >> At 03:23 PM 8/29/2005, Scott Stanfield wrote: >> >>> I can view data in their vcustomer table but it gives me errors >>> when I try to change and address from within R:base. >> >> >> Scott, >> >> Technically, it means that you don't have the rights/privileges >> to update/modify database using their native ODBC driver. >> >> Check the access rights, etc., and then SCONNECT the system DSN >> using the owner password. >> >> Hope that helps! >> >> Very Best R:egards, >> >> Razzak. > >
