Re: Unable to open entire project via ODBC to SQL server

From: Rod Gill (rod)
Date: 01/21/05 

Date: Fri, 21 Jan 2005 22:00:53 +1300

Failing a rights issue it looks like a corruption of some sort. In the
original workstation open the project, save to .mpp, delete the project in
SQL Server then open the .mpp file and re-save to SQL Server. I would also
get all workstations onto the same MDAC release. 

-- 
Rod Gill
Project MVP
"Maurice Birchler" <MauriceBirchler@discussions.microsoft.com> wrote in 
message news:BF5D9F26-1B03-4FAB-862B-812756B2287B@microsoft.com...
> Thanks, but it is not that. It is something to do with the Workstation ID
> that stops MS-Project from being able to open the entire project, 
> restricting
> it to an import via a map. It seems that only the workstation that created
> the project database via MS-Project SaveAs can open it completely.
>
> "Rod Gill" wrote:
>
>> When a project is opened from a database, Project sets a flag that says 
>> "Hey
>> this user has this project open, so you can only have read only access". 
>> The
>> flag is reset when the project is closed. Sometimes if Project crashes, 
>> this
>> flag gets left set and needs manual clearing: it's in the MSP_Projects
>> table. Read projdb.htm for details (It's in one of project's program
>> folders).
>>
>> As a general point for data integrity and reliability, all pc's should be 
>> on
>> the same MDAC release: the latest is 2.8  This isn't essential, but can
>> avoid some issues.
>>
>> -- 
>>
>> Rod Gill
>> Project MVP
>>
>>
>> "Maurice Birchler" <MauriceBirchler@discussions.microsoft.com> wrote in
>> message news:FE5054CE-59DE-428D-B999-0FB4A7CC3742@microsoft.com...
>> > The workstation that created the Project has no problem, however 
>> > another
>> > workstation running a slightly older version of the ODBC driver does 
>> > not
>> > get
>> > full access to the project tables using same version of MS-Project 2000 
>> > to
>> > SQL 7.0
>> >
>> > Yet MS-Query has no problem querying and updating the tables in the
>> > database. Both users have ownership rights to the SQL database.
>> >
>> > What is it in MS-Project that appears to lock a database down to the 
>> > name
>> > of
>> > the SQL Database owner and excludes other users with same rights?
>> >
>>
>>
>>

Relevant Pages

  • Re: Unable to connect to server
    ... This posting is provided "AS IS" with no warranties, and confers no rights. ... > Cannot open user default database. ... > C:\Program Files\Microsoft SQL ...
    (microsoft.public.sqlserver.security)
  • Re: Understanding SQL and Microsoft GP
    ... You shouldn't even need DBO rights. ... DBA and having him profile a session where the Excel reports are being run. ... SQL Server MVP ... access to SQL server because I have no database knowledge. ...
    (microsoft.public.sqlserver.security)
  • Re: Which Method to Create a Database Do I Use?
    ... BTW, I am still completely in the dark as to if I need to download SQL Express Edition because I don't have yet have any software that will allow a database connection to run on my computer, or because you assumed for some reason that I only want to use SQL Express Edition. ... To be fair, VS is a "generic" tool designed to front a variety of backend databases, but each of the serious engines have rights management needs as well. ... Hitchhiker's Guide to Visual Studio and SQL Server ...
    (microsoft.public.dotnet.framework.adonet)
  • Re: activate multiple users
    ... You must provide read/write permissions for the folder for all users who ... need to access the database. ... User will also have to have delete rights as ... The other workstation got the acces to the ...
    (microsoft.public.access.security)
  • Re: Managing SQL database rights using AD
    ... The problem I am trying to solve is managing SQL database rights using AD. ... --- Org1 admins ...
    (microsoft.public.sqlserver.security)
Loading