When i created tables in sql they appeared in my adp project by name + (dbo). In my VBA code everytime I refered to a table I qualified it with dbo. I then distributed this to other users and everything worked fine. This was the test db.
The database was then moved to the production server and I was given by the sa the user name dbo (they said they did this by running the stored procedure sp_changedbowner). To me it looks like nothing has changed with regards to my permissions but Now when I open my adp the tables no longer have a qualifier (ie dbo) after the name and i get an error messages when it reads code such as:
me.uniquetable = "dbo.tablename" on loading the adp form. And I also can no longer enter data into new tables i create even though i am the dbo.
Other users are fine as before.
The sa says it's my problem but I think it something they have done. I use integrated Windows authentication for login.
Can anyone please help who has experience of being the sa
Thanks
The database was then moved to the production server and I was given by the sa the user name dbo (they said they did this by running the stored procedure sp_changedbowner). To me it looks like nothing has changed with regards to my permissions but Now when I open my adp the tables no longer have a qualifier (ie dbo) after the name and i get an error messages when it reads code such as:
me.uniquetable = "dbo.tablename" on loading the adp form. And I also can no longer enter data into new tables i create even though i am the dbo.
Other users are fine as before.
The sa says it's my problem but I think it something they have done. I use integrated Windows authentication for login.
Can anyone please help who has experience of being the sa
Thanks