Using ODBC in MOPS2007?

[Quizzed again]

I am curious about possible uses of the ODBC option for opening project in
MSP2007 Server. What are the possible advantages or usage scenarios?
Thanks for the general education.

 

[Ben Howard [MVP]]

Hi Quizzed,
ODBC was dropped from Project Server 2003 because it was too "chatty" and
"heavy" as a protocol to work in the new web based, vpn based world. These
are the cons.

 

[Dale Howard [MVP]]

Quizzed again --

The ODBC button appears in the Open dialog to help an organization during
its implementation of Project Server 2007 when the organization had
previously saved their projects in an ODBC compliant database, such as SQL
Server, but WITHOUT using Project Server 2003 previously. For example, when
using Microsoft Project 2003 WITHOUT Project Server 2003, an organization
could set up a SQL Server database, and then the PMs could save their
projects in that SQL database.

So, if an organization was implementing Project Server 2007 and all of the
projects were saved in a non-Project Server 2003 SQL Server database, then
PMs would use the ODBC button in the Open dialog to open their current
projects before they save them in the Project Server 2007 database. Hope
this helps.

 

[Quizzed again]

Ok Ben and Howard those are good explanations. Understand that I am a
tinkerer, so I am going nowhere but wandering around for new ideas and the
idea coming to mind is to recreate the old "version" feature of MOPS2003.

Could I copy my database (maybe using playbook) and then create a link to
the copy using ODBC to open those files? Why? Well because then I could have
a whole database of interconnected files that I could edit or massively
change and not impact the source files (sort of like "version" did in
MOPS2003)?
Maybe good? Not good?
Better left untouched?

Thanks!

 

[Rod Gill]

Hot potatoe!

Microsoft specifically doesn't support that. Much of Project's data in an
old ODBC save was still in binary fields and the slightest mistake could
corrupt the entire project.

Especially in 2007 onwards I would recommend not even thinking about doing
this! Corruption of the Project Server implementation is another
possibility.

If you want to manipulate project data in project server itself, the only
safe way is either using the PSI programming interface or VBA in Project
Professional.

--

Rod Gill
Microsoft MVP for Project - http://www.project-systems.co.nz

Author of the only book on Project VBA, see: http://www.projectvbabook.com

Ok Ben and Howard those are good explanations. Understand that I am a
tinkerer, so I am going nowhere but wandering around for new ideas and
the
idea coming to mind is to recreate the old "version" feature of MOPS2003.

Could I copy my database (maybe using playbook) and then create a link to
the copy using ODBC to open those files? Why? Well because then I could
have
a whole database of interconnected files that I could edit or massively
change and not impact the source files (sort of like "version" did in
MOPS2003)?
Maybe good? Not good?
Better left untouched?

Thanks!



__________ Information from ESET Smart Security, version of virus
signature database 4916 (20100304) __________

The message was checked by ESET Smart Security.

http://www.eset.com

__________ Information from ESET Smart Security, version of virus signature database 4916 (20100304) __________

The message was checked by ESET Smart Security.

http://www.eset.com

 

[Gary L. Chefetz]

I think the preferred path to a database in 2007 and higher, is via XML. I
wonder if ODBC was dropped for other reasons that are more marketing driven.

--
Gary L. Chefetz, MVP, MCT, MCTIP
Business: http://www.msprojectexperts.com
FAQs: http://www.projectserverexperts.com
BLOG: http://www.projectserverhelp.com

 

[Quizzed again]

Rod! Thank you for the information!

Hot potatoe!

Microsoft specifically doesn't support that. Much of Project's data in an
old ODBC save was still in binary fields and the slightest mistake could
corrupt the entire project.

Especially in 2007 onwards I would recommend not even thinking about doing
this! Corruption of the Project Server implementation is another
possibility.

If you want to manipulate project data in project server itself, the only
safe way is either using the PSI programming interface or VBA in Project
Professional.

--

Rod Gill
Microsoft MVP for Project - http://www.project-systems.co.nz

Author of the only book on Project VBA, see: http://www.projectvbabook.com






__________ Information from ESET Smart Security, version of virus signature database 4916 (20100304) __________

The message was checked by ESET Smart Security.

http://www.eset.com



.

 

[Quizzed again]

Gary I appreciate your help!

I think the preferred path to a database in 2007 and higher, is via XML. I
wonder if ODBC was dropped for other reasons that are more marketing driven.

--
Gary L. Chefetz, MVP, MCT, MCTIP
Business: http://www.msprojectexperts.com
FAQs: http://www.projectserverexperts.com
BLOG: http://www.projectserverhelp.com


.