Can not see columns in query "Design View"

Even though I select "Column Names" in Design View when creating a query (or view), only "* (All Columns)" appears in the table box.

In InfoPath, when I connect a combo-box, err drop down box, to the database, I am unable to connect directly to a table... no tables are shown. If I select a different database, these problems do not exist.

I can not find any setting to allow these columns to be shown in the design view or any setting that will "expose" the tables in InfoPath.

I tried creating a new database and exporting the data, tables and data, from the troubled DB to the new DB; however, the new DB exhibited the same behaviour. The system tables, Master and Model, have the same behaviour. Please help me with your ideas and suggestions... thank you very much for your time.

This database was upsized from Access 2003 to SQL Server 2000 SP4.

rogge

I'm not sure what you're talking about here - can you include a screenshot?|||

here is a screen shot for the Views in SQL Server

http://community.roggeheflin.com/media/screenShot.bmp

and from InfoPath:

http://community.roggeheflin.com/media/spsConnectionTables.bmp

http://community.roggeheflin.com/media/spsConnectionTablesNone.bmp

thank you for your help!

|||

I can't access the screenshots from these links, but I'll take a shot at the troubleshooting process for them anyway.

Try and connect to the database using Enterprise Manager (if you're using SQL 2000) or Management Studio (if you're using SQL 2005). Make sure that you know the account you're connecting with.

Verify that you can see all of the tables and columns you're interested in.

Next, check the connection account you're using in InfoPath. To do this, you may need to check the documentation or the InfoPath newsgroups, since I'm not as familiar with that product as SQL.

If you're still not able to see the tables, run the SQL Profiler tool to see what is happening when you try to connect to the server. You can learn more about that here:

http://www.informit.com/guides/content.asp?g=sqlserver&seqNum=199&rl=1

Use the trace items that show connection information in addition to what is talked about in this article. That should show you who is trying to connect and what they are running as a command. This should get you closer to the problem (and the answer).

Buck

|||it had somehting to do with object permissions...thank you for your help|||

Glad to hear that you've solved it.

Buck