RJV
asked on
Database table is not visible. How to make it visible?
I created a database with MS SQL Management Sudio and added a database to it. For now logging in is through the Windows NT authentication. My problem is that I am working on an application and plan and ODBC access to the database and table. I'm able to log on to the database. However the app cannot find the table. I compiled a Microsoft app that lists all tables under that database. Surprisingly, it lists all System Tables, all dbo schemas, and others not even shown in Management Studio. Yet my table is nowhere to be seen, though it is also listed in Management Studio as a dbo schema.
How do I make that visible? It seems to be some restriction in terms of security or similar but I don't know where to look, as I've tried comparing the other accesses (Master, etc) that are there.
How do I make that visible? It seems to be some restriction in terms of security or similar but I don't know where to look, as I've tried comparing the other accesses (Master, etc) that are there.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Looking through Management Studio, everything seems to have security related to it, from the logical users and data to the schema. Right now all I do is log on to the OS and then load Management Studio, with SQL starting up as the usual service. As to the app, I set it also to the same security as the OS. Evidently, not good enough though all I want is something simple. Try to change it and I also have to settle to what is built in. So, having said that, might you suggest what I check out exactly, even if to create another table and/or database. I want to simplify however much I can.
try to give necessary permissions to BUILTIN/Administrators for the database. normally we give sysadmin permissions to this user id.
try to do it check whether the you are able to view the table for windows authentication login.
bye.
try to do it check whether the you are able to view the table for windows authentication login.
bye.
ASKER
The not so unusual amazing thing. When I posted the question here I suspected of a permissions issue, or something done wrong in Management Studio. Of course, it could also be at the ODBC level or even my code. After looking everything over I decided to ask those who know SQL better (not my goal; suffice to suffer with C++, MFC, threads, etc). As it turned out, you also wondered about permissions. Thus I focused more on that area, in as much as that is possible in Management Studio.
Late yesterday, after over scratching my head, I decided to set this checkbox in ODBC:
Change the default database to:
...and then select the database I had already selected to access. Why hadn't I done that before? It didn't and does not make sense. Let's face it, I had accessed that very same database and even test connected to it. Well, that did the trick! I hope this helps you or anyone else here in the future.
So, while I didn't get a specific solution to my problem, thanks to your pointers I was better able to zero in. So I will award the points in thanks for effort that led to the solution.
Late yesterday, after over scratching my head, I decided to set this checkbox in ODBC:
Change the default database to:
...and then select the database I had already selected to access. Why hadn't I done that before? It didn't and does not make sense. Let's face it, I had accessed that very same database and even test connected to it. Well, that did the trick! I hope this helps you or anyone else here in the future.
So, while I didn't get a specific solution to my problem, thanks to your pointers I was better able to zero in. So I will award the points in thanks for effort that led to the solution.
ASKER