DBinPhilly
12-18-2012, 10:56 AM
SOLVED: Problem was in permissions.
I have very limited experience with SQL Server. I last installed an Access .adp program about 7 years ago, but am forced to work on one again.
Because of space limitations, the database has been transferred to a new version of SQL Server (2000 to 2005) on a different server and now my .adp program won't work.
All of the tables in the new SQL database appear to have (dbo) associated with it - which means database owner, I guess.
When I refer to the tables in VBA, sometimes the tables are not recognized. I have a user table and VBA tells me there are no records in the table (or maybe it doesn't even see the table), while I know there are a dozen records. The table is named "Users".
I use the following VBA statement to name the table:
rst1.Open "Users", cnn1, adOpenForwardOnly, adLockReadOnly
I've tried changing it to the following:
rst1.Open "dbo.Users", cnn1, adOpenForwardOnly, adLockReadOnly
Neither statement returns data from the table.
I know this is a SQL Server 101 kind of a problem.
Anyone know what I'm doing wrong?
I have very limited experience with SQL Server. I last installed an Access .adp program about 7 years ago, but am forced to work on one again.
Because of space limitations, the database has been transferred to a new version of SQL Server (2000 to 2005) on a different server and now my .adp program won't work.
All of the tables in the new SQL database appear to have (dbo) associated with it - which means database owner, I guess.
When I refer to the tables in VBA, sometimes the tables are not recognized. I have a user table and VBA tells me there are no records in the table (or maybe it doesn't even see the table), while I know there are a dozen records. The table is named "Users".
I use the following VBA statement to name the table:
rst1.Open "Users", cnn1, adOpenForwardOnly, adLockReadOnly
I've tried changing it to the following:
rst1.Open "dbo.Users", cnn1, adOpenForwardOnly, adLockReadOnly
Neither statement returns data from the table.
I know this is a SQL Server 101 kind of a problem.
Anyone know what I'm doing wrong?