Project 98 to 2003 ODBC tables

[Peter Lock]

Greetings

We have just upgraded our workstations here to XP with Office 2003 (Project
2003 Pro). Previously we used Windows 200o with Project 98.

We have a custom dll written by a 3rd party company that uses vb code to
save data in Project to an ORacle database using ODBC. It would appear that a
{Project}.FileSaveAs would use a table called PROJECT_INFORMATION, now the
same dll (modified to reference Project 2003) creates the table MSP_PROJECTS
(amoungst others).

Is there a way to tell Project 2003 to use older 98 table names when saving
a new project or that hard coded? Also is there a quick way to convert all
our existing projects to the new table format, and if I did this would that
mean those people that are still on Project98 not be able to use the new
table structure.

Whew!!
Anyway I think I am in for some long nights fixing up the coding as it
refers to the table names directly in the dll with it's select queries.

Any help would be appreciated.

Cheers
Peter Lock
Technical Support Specialist
Australian National Audit Office

 

[JackD]

Sorry,
The database structure between project 98 and project 2003 is VASTLY
different. There is not a 1:1 mapping between the old tables and fields and
the newer ones. I'd consider it a fairly difficult thing to work around.

As far as I know Project 2003 can not save to a project 98 database.

The quick way to convert the projects to the new structure is to open them
with Project 2003 and save them in database form. This will convert them but
will also make them unreadable by project 98.

 

[Peter Lock]

Hi Jack

Thanks for your reply. I guess I was looking for a simple way to run the two
systems together during the upgrade. We will just have to freeze any new
projects or changes during that time.

Thanks again
Peter Lock