|
Jon T.
7/27/2007 1:53 PM
|
[ Severity set to Critical ]
|
Matt R.
7/27/2007 2:34 PM
|
[ Priority changed from unassigned to Scheduled ]
|
Matt R.
7/27/2007 2:41 PM
|
Sounds like you are accessing the database as a different user than the schema it was created as.
For instance...
If you have a database running under user "centric_crm", then backup the database and restore it on another system, the restored database needs to be associated with either the "centric_crm" user or mapped to another user. There is some complexity in remapping so I usually keep it as the same username. There are scripts to remap, and I can dig one up if you need.
The error is indicating that the user you are accessing the data as does not see the [access] table, but would see [centric_crm.access] instead.
Is this the scenario you are seeing this error as?
|
|
Jon T.
7/30/2007 4:34 PM
|
The error we are getting is - * Access: Invalid object name 'access'.
We have not changed the centric_crm user and it is still listed as a database user for centric.
I have setup an ODBC connect from my PC to the centric db using the centric_crm user and it works fine.
I have unattached and reattached the db, and recreated the centric_crm user but this has not helped.
If you have any ideas it would be greatly appreciated.
Many Thanks,
Jon
|