Thanks Dave,
line terminators - arh yes, that will be it ;-). All other projects that I use CVS with have unix style line terminators.
Should have cottoned on to that one myself as I did look at the buildall.bat file and noticed that it was unreadable using notepad!
Been a long time since I did any real Windows programming and even longer when it comes to VB - 6 years.
I'm not trying to modify pgAmin II, just use it as a starting point/ reference on how you used ADO to connect to postgreSQL.
I have to write some code to publish data from a postgresql database to Reuters using an xl spread sheet - yuk, thought I'd check out your code to give me a head start...
thanks again,
Regards
Donald Fraser.
----- Original Message -----
Sent: Tuesday, August 17, 2004 8:56 AM
Subject: RE: [pgadmin-support] load project problems with pgAdmin II
Hi,
I'm trying to load up the old pgAdmin II source but running into some problems.
OK, you know we're not actively supporting pga2 any more, but seeing as it's you... :-)
1) I have followed the instructions - uninstalled any installations, registered the DLL's in the binaries directory and pgAdmin2.exe runs ok from that directory.
OK.
2) I manually edit the pgadmin2.vbp file to ensure that the paths to the Reference libs are correct, example:
Reference=*\G{00000200-0000-0010-8000-00AA006D2EA4}#2.0#0#..\..\..\..\Program Files\Common Files\System\ADO\msado20.tlb#Microsoft ActiveX Data Objects 2.0 Library
You shouldn't need to do that. It should use the guid's to find things - in my experience the paths are more like comments.
3) I have Microsoft Visual Studio 6.0 SP5 installed.
OK.
4) I attempt to open the Visual basic project file pgadmin2.vbp and I get the following message:
Errors during load. Refer to "C:\Projects\pgadmin\pgadmin2\pgadmin2\frmMain.log"
frmMain.log contains the following lines:
'0' could not be loaded
Line 0: The file C:\Projects\pgAdmin\pgadmin2\pgadmin2\frmMain.frm could not be loaded.
I wonder if this is a unix/dos line endings problem. When you checkout the files, make sure that dos line endings is switched on (this is an option in WinCVS, dunno about other clients.
Regards, Dave.
