Kay,
fogive the vagueness of this reply but I can't remember the exact
search words in google to find *exactly* it.
I've read about this but haven't experianced this issue myself... I
think it comes down to what Paul was hinting at
"While this will create the necessary login IDs, what it will n
Sent: Monday, 20 February 2006 8:27 AM
To: cfaussie@googlegroups.com
Subject: [cfaussie] Re: perplexing SQL Server database permissions problem
On 2/20/06, darryl lyons <[EMAIL PROTECTED]> wrote:
> Paul Hastings is on the money. I've seen this a lot. It's usually when
> the
On 2/20/06, darryl lyons <[EMAIL PROTECTED]> wrote:
> Paul Hastings is on the money. I've seen this a lot. It's usually when the
> user used to create a database object is not the default DBO. In the owner
> column in the table view in EM, is DBO next to the table name?
I have remote desktop acce
On 2/20/06, David Harris <[EMAIL PROTECTED]> wrote:
> questions:
> 1. is it an MSSQL DB?
Yep, 2K.
> 2. have you restored the DB from another MSSQL server?
No, but I am beginning to suspect something like this has happenend.
The client didn't respond to that portion of my email.
> 3. Are you us
Paul Hastings is on the money. I've seen this a lot. It's usually when the user used to create a database object is not the default DBO. In the owner column in the table view in EM, is DBO next to the table name?Darryl
On 2/20/06, Kay Smoljak <[EMAIL PROTECTED]> wrote:
My apologies to anyone who is
Hi Kay,
questions:
1. is it an MSSQL DB?
2. have you restored the DB from another MSSQL server?
3. Are you using the same MSSQL server User name and password?
If so, I have seen problems like this a bit, and the only work round I
have found is to delete the user from the DB, and re-add them
K
