Razzak - Scott, A readOnly ODBC driver for accounting systems is not unusual. Rather than creating a generic userID that would allow read/write to certain tables (like customer profile, info), the vendor usually opts to just not allow _any_ external program to modify the dataset.
----- Original Message ----- From: "A. Razzak Memon" <[EMAIL PROTECTED]> To: "RBASE-L Mailing List" <[email protected]> Sent: Monday, August 29, 2005 3:16 PM Subject: [RBASE-L] - Re: R:BASE ODBC Connection to MAS200/90 > At 03:59 PM 8/29/2005, Scott Stanfield wrote: > >>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. > > Scott, > > They simply don't want you to have the full access to their > database! Not an unusual answer. > > Let them know that R:BASE does NOT corrupt any SCONNECTed > database. > > Very Best R:egards, > > Razzak. > > > >>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. >
