Issues: MSP98 to MSP2003 Conversion

[AHP]

Hi all,
I have the unenviable task of converting a customized MSP98 environment to a
new MSP2003 environment.

Background
--------------
The old MSP98 front-end has 6 customized buttons
1. SAVE project plan to SQL Database
2. OPEN project plan from SQL Database
3. FILTER project plans on the SQL Database
4. CHANGE user access of plans on the SQL Database
5. REGISTER new project plan on the SQL Database
6. MODIFY an existing plan on the SQL Database

Each button is a seperate Add-In written in VB6 and integrated into MSP98.
The source code for these buttons/Add-Ins is lost.
The current MSP98 environment does NOT use Project Server, but does save the
project plans to a SQL Server database.

The new MSP2003 environment must be tailored with Add-Ins that perform the
identical functions to the current MSP98 environment.
The same SQL Server will be used, but the database on the server will be
different.
The new environment will NOT use any version of Project Server.
The Add-Ins must be written in VB.NET or C#
The new solution must perform better than the old solution over a WAN/LAN.

I have never written an Add-In in my life, but am fluent in VB6, competent
in C#, competent with SQL Server 6.5 - SQL Server 2000. I have very little
experience with MS Project as a product, beyond very simple project plans.

Issues:
--------
Given the above constraints ...
1. Where can I get the SQL Server scripts to build the database schemas for
both MSP98 and MSP2003 projects? (I found some scripts in the MSP98 CD's
ValuePack directory, but can't find equivalent scripts on the MSDN DVD).
2. What would be the best language to write the Add-Ins in?
3. Does each button have to be a seperate Add-In? Or can it be one solution
with 6 buttons? Which technique will be best?
4. What snags and issues am I going to face converting between MSP98 and
MSP2003, and are there any differences in the database layouts?

Any help at all will be appreciated.

PS. I will only be reading the responses to this post on Monday 6 September

 

[Mark Durrenberger]

I can't answer all of your questions, but I can speak(write) to Question 3.
The only reason I can come up with for splitting your code into several
add-ins would be to allow deployment of different features to different
users. If every user is getting the same code, they you can put it all in
one add-in.

Since you are fluent in VB6 you might consider developing in VB.net.
Mark


--
_________________________________________________________
Mark Durrenberger, PMP
Principal, Oak Associates, Inc, www.oakinc.com
"Advancing the Theory and Practice of Project Management"
________________________________________________________

The nicest thing about NOT planning is that failure
comes as a complete surprise and is not preceded by
a period of worry and depression.

- Sir John Harvey-Jones

Hi all,
I have the unenviable task of converting a customized MSP98 environment to a
new MSP2003 environment.

Background
--------------
The old MSP98 front-end has 6 customized buttons
1. SAVE project plan to SQL Database
2. OPEN project plan from SQL Database
3. FILTER project plans on the SQL Database
4. CHANGE user access of plans on the SQL Database
5. REGISTER new project plan on the SQL Database
6. MODIFY an existing plan on the SQL Database

Each button is a seperate Add-In written in VB6 and integrated into MSP98.
The source code for these buttons/Add-Ins is lost.
The current MSP98 environment does NOT use Project Server, but does save the
project plans to a SQL Server database.

The new MSP2003 environment must be tailored with Add-Ins that perform the
identical functions to the current MSP98 environment.
The same SQL Server will be used, but the database on the server will be
different.
The new environment will NOT use any version of Project Server.
The Add-Ins must be written in VB.NET or C#
The new solution must perform better than the old solution over a WAN/LAN.

I have never written an Add-In in my life, but am fluent in VB6, competent
in C#, competent with SQL Server 6.5 - SQL Server 2000. I have very little
experience with MS Project as a product, beyond very simple project plans.

Issues:
--------
Given the above constraints ...
1. Where can I get the SQL Server scripts to build the database schemas for
both MSP98 and MSP2003 projects? (I found some scripts in the MSP98 CD's
ValuePack directory, but can't find equivalent scripts on the MSDN DVD).
2. What would be the best language to write the Add-Ins in?
3. Does each button have to be a seperate Add-In? Or can it be one solution
with 6 buttons? Which technique will be best?
4. What snags and issues am I going to face converting between MSP98 and
MSP2003, and are there any differences in the database layouts?

Any help at all will be appreciated.

PS. I will only be reading the responses to this post on Monday 6

September

 

[Rod Gill]

Hi,

Performance wise, VBA macros will run faster than an addin as they run in
the same space/program instance.
When opening and saving a project, the speed will be the same or slower than
for Project 98 because Project 2003 has more data to save. If performance is
a real issue, then look at using Terminal Services or Citrix servers next to
the SQL Server to run Project.

You can add buttons or menus in VBA to run your code..

--
For VBA posts, please use the public.project.developer group.
For any version of Project use public.project
For any version of Project Server use public. project.server

Rod Gill
Project MVP
For Microsoft Project companion projects, best practices and Project VBA
development services
visit www.projectlearning.com/

Hi all,
I have the unenviable task of converting a customized MSP98 environment to a
new MSP2003 environment.

Background
--------------
The old MSP98 front-end has 6 customized buttons
1. SAVE project plan to SQL Database
2. OPEN project plan from SQL Database
3. FILTER project plans on the SQL Database
4. CHANGE user access of plans on the SQL Database
5. REGISTER new project plan on the SQL Database
6. MODIFY an existing plan on the SQL Database

Each button is a seperate Add-In written in VB6 and integrated into MSP98.
The source code for these buttons/Add-Ins is lost.
The current MSP98 environment does NOT use Project Server, but does save the
project plans to a SQL Server database.

The new MSP2003 environment must be tailored with Add-Ins that perform the
identical functions to the current MSP98 environment.
The same SQL Server will be used, but the database on the server will be
different.
The new environment will NOT use any version of Project Server.
The Add-Ins must be written in VB.NET or C#
The new solution must perform better than the old solution over a WAN/LAN.

I have never written an Add-In in my life, but am fluent in VB6, competent
in C#, competent with SQL Server 6.5 - SQL Server 2000. I have very little
experience with MS Project as a product, beyond very simple project plans.

Issues:
--------
Given the above constraints ...
1. Where can I get the SQL Server scripts to build the database schemas for
both MSP98 and MSP2003 projects? (I found some scripts in the MSP98 CD's
ValuePack directory, but can't find equivalent scripts on the MSDN DVD).
2. What would be the best language to write the Add-Ins in?
3. Does each button have to be a seperate Add-In? Or can it be one solution
with 6 buttons? Which technique will be best?
4. What snags and issues am I going to face converting between MSP98 and
MSP2003, and are there any differences in the database layouts?

Any help at all will be appreciated.

PS. I will only be reading the responses to this post on Monday 6

September