oraOLEDB connection

I am having problem when I am fetching a data column having a data type long and connecting to the database with provider oraOLEDB.
 The table emp having the long data type column has been created in a user "mainuser". I have created another user "moduser". I have giving all the permission of select, delete, insert to mod on the table emp.
Now when I am logining from VB by "mainuser" I am able to fetch the record from table emp. If I login as "moduser" I get an error "Table or View does not exist" on fetch of record.
With the same situtation of two user as above I use MSDAORA as the provider I don't have problem in both the situation.
Who is Participating?
Mohammed NasmanConnect With a Mentor Software DeveloperCommented:
try to put the owner of table before the table name

mainuser.emp instead of just emp

or create public Synonym for ur table

Anthony PerkinsCommented:
Please maintain your open questions:
Questions Asked 13
Last 10 Grades Given A A A A A A C B  
Question Grading Record 8 Answers Graded / 8 Answers Received

The more common way to handle this is to grant all on table emp to Public

And then make sure that mainuser and mod user are both in the Public group.  Then, you can reference your table name as emp in both your queries and your VB code.

Normally, it's a bad idea to write an application where specific users own database objects such as queries.  dbo or whomever is the database owner should own all objects in the database, tables, procs etc.

You can log in as mainuser and create a table under the dbo if you are part of the dbo group, simply by including the dbo in the create table or create procedure statements:

create table dbo.emp .......

In this way, even if mainuser creates the table it will belong to DBO.  If mainuser and moduser are both part of DBO then both will have all rights automatically.
Keep up with what's happening at Experts Exchange!

Sign up to receive Decoded, a new monthly digest with product updates, feature release info, continuing education opportunities, and more.

Because of the fude between MS and Oracle only use MSDAORA and not oraOLEDB.
Hi saurabh_pradhan,
It appears that you have forgotten this question. I will ask Community Support to close it unless you finalize it within 7 days. I will ask a Community Support Moderator to:

    Split points between: mnasman and mdougan

saurabh_pradhan, if you think your question was not answered at all or if you need help, just post a new comment here; Community Support will help you.  DO NOT accept this comment as an answer.

EXPERTS: If you disagree with that recommendation, please post an explanatory comment.
DanRollins -- EE database cleanup volunteer
per recommendation

Community Support Moderator @Experts Exchange

mdougan points for you at:
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.