I've beem doing Client/Server with VFP5 and SQL 6.5 and Oracle 7.3 & 8.0 and this is exactly right. You don't need to be owner to add, edit, update and delete Oracle tables.

You can on the other hand easily become a victim to a tool bigot. These guys are running rampant in the Oracle camp.


>>I'm having trouble creating a remote view on an Oracle 8 server (UNIX, on a Digital Alpha box). I get the error:
>>
>>"Connectivity Error: ORA-00942: table or view does not exist".
>>
>>I talked about this to our DBA, and he says it's because I don't "own the table". He also says that I'm "never going to own the table" so I should "forget about using Visual FoxPro."
>>
>>We don't have any problems connecting to the Oracle server with Access or InfoMaker, just with VFP.
>>
>>The tables we are tying to access are read only data dumps from our mainframe. I'd like to show off VFPs prowess as a front end to our data warehouse, but I'm just not getting very far with the DBA. Any Suggestions?
>>
>
>Your DBA sounds like he's a jerk, lazy, not a very good [knowledgeable] DBA, or just flat biased against VFP. The front end has nothing to do with accessibility of an Oracle table. If that were true, much of the Internet would be dead.
>
>Oracle access priveleges to specific objects/data have everything to do with accessibility [once SQL*Net, ODBC and a DSN have been set up correctly]. You do not have to be the owner of an Oracle table to have SELECT privileges on the data. Access can be established many ways:
>
>[1] An Oracle SYNONYM [e.g., The synonym for UserID.TableName is set to TableName] can be set up for the table with users granted privileges.
>
>[2] The DBA can create a ROLE with privileges granted to the ROLE for selecting data from the table. Then users can be granted that ROLE.
>
>[3] An Oracle view with all or selected columns from the table can be created by the DBA with users or Roles granted privileges to that view.
>
>[4] Mix and match any of the above.
>
>Don't let DBAs get away with this nonsense.