Re: Connecting MS Project 2003 Pro to a MySQL 5 database with MyOD
- From: Rob Schneider <rmschne_removethis_bit@xxxxxxxxx>
- Date: Thu, 23 Apr 2009 17:23:30 +0100
Yes. perhaps in the spirit of MySQL start an open source project to do so?
kevin wrote:
Yes, I've read the file PJDB.HTM which describes the data format..
But it could be better it there was a script file to load SQL directly.
Kevin
"Rob Schneider" wrote:
Have you seen the file projdb.htm which is installed somewhere on your Project installation folder tree?
kevin wrote:Thank you Jack for this link, it proves that MS Project could work with MySQL.
Now, if I try to load the schema first, it seems to be OK, I can save the project.
But when I reopen it, I get a message about "circular relationship" in some tasks and some information is lost (task finish dates, blank spaces between two tasks...) while the project is still open.
Do you know if there is an "official" SQL schema for this database?
Kevin.
"Jack Dahlgren" wrote:
I do not believe that MySQL is supported by MS Project so you are basically on your own. Looks like it needs some hand tweaking - loading the schema first, setting some parameters.
This appears to be a reasonable starting point:
http://bugs.mysql.com/bug.php?id=17508
-Jack Dahlgren
http://zo-d.com/park-information
"kevin" wrote:
Hello,
I am trying to connect MS Project Professional 2003 to a MySQL 5 database but it doesn't work.
First I created an ODBC source when I do "save as" in the File menu, click on "ODBC...", create a new data source using "MySQL ODBC 5.1 Driver" (also tried 3.51 version, no success). The connection seems good but when I save the project into the database I get this error message :
[MySQL][ODBC 5.1 Driver][mysqld-5.1.32-community-log]You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax near 'LONGCHAR , PROJ_OPT_CALC_COSTS BIT , PROJ_PROP_CATEGORY LONGCHAR , PROJ_PR' at line 1
I found the same issue on MySQL Bugs : http://bugs.mysql.com/bug.php?id=17178 and no solution.
How to fix this bug ? I don't think it comes from the ODBC, but from the SQL syntax : the type LONGCHAR doesn't exist.
Thanks by advance,
Regards.
- References:
- Connecting MS Project 2003 Pro to a MySQL 5 database with MyODBC
- From: kevin
- RE: Connecting MS Project 2003 Pro to a MySQL 5 database with MyODBC
- From: Jack Dahlgren
- RE: Connecting MS Project 2003 Pro to a MySQL 5 database with MyOD
- From: kevin
- Re: Connecting MS Project 2003 Pro to a MySQL 5 database with MyOD
- From: Rob Schneider
- Re: Connecting MS Project 2003 Pro to a MySQL 5 database with MyOD
- From: kevin
- Connecting MS Project 2003 Pro to a MySQL 5 database with MyODBC
- Prev by Date: Re: Order of customized views in View menu
- Next by Date: Re: Lead Time in Project
- Previous by thread: Re: Connecting MS Project 2003 Pro to a MySQL 5 database with MyOD
- Next by thread: Resource Team
- Index(es):
Relevant Pages
|