Skip site navigation (1) Skip section navigation (2)

Re: Compiling using Visual Studio 2003

From: Paul Cochrane <paul(dot)m(dot)cochrane(at)tuht(dot)scot(dot)nhs(dot)uk>
To: pgsql-odbc(at)postgresql(dot)org
Subject: Re: Compiling using Visual Studio 2003
Date: 2005-02-10 15:22:37
Message-ID: 420B7C3D.8030507@tuht.scot.nhs.uk (view raw or flat)
Thread:
Lists: pgsql-odbc
Dave Page wrote:

> 
>
>  
>
>>-----Original Message-----
>>From: pgsql-odbc-owner(at)postgresql(dot)org 
>>[mailto:pgsql-odbc-owner(at)postgresql(dot)org] On Behalf Of Paul Cochrane
>>Sent: 10 February 2005 14:32
>>To: pgsql-odbc(at)postgresql(dot)org
>>Subject: Re: [ODBC] Compiling using Visual Studio 2003
>>
>>Dave Page wrote:
>>
>>    
>>
>>>>Off topic,  FYI, I couldn't get the command line nmake to 
>>>>        
>>>>
>>work. I did 
>>    
>>
>>>>try putting in extra search paths & stuff but gave up shortly 
>>>>thereafter 
>>>>and continued my fight with the IDE.
>>>>   
>>>>
>>>>        
>>>>
>>>That's how I build it all the time. Did you run vcvars32.bat 
>>>      
>>>
>>first? That
>>    
>>
>>>should be all that is needed.
>>>
>>> 
>>>
>>>      
>>>
>>I'm Thick. What is this file? It doesn't seem come with psqlodbc and 
>>there is no mention of it in the doc on the GBORG site about 
>>compiling 
>>the driver. I was changing to the extracted dir & trying nmake.....
>>    
>>
>
>It sets up the DOS environment for VC and is part of Visual Studio. On
>my system I have it in:
>
>C:\Program Files\Microsoft Visual Studio .NET 2003\Vc7\bin (VS.NET 2K3)
>
>And
>
>C:\Program Files\Microsoft Visual Studio\VC98\Bin (VS6)
>
>Note that if you can it's better to use VC++6 as the required runtimes
>are generally already on most machines.
>  
>
Good show. I can now compile using the makefile.  Maybe you can add this 
info to run vcvar32.bat to the readme.txt file? I did read this file but 
knew nothing about running the batch file beforehand (not knowing much 
about visual studio).

>>I can fix it in code but this would break the compatibility of using 
>>either the paradox tables or postgres tables. I would have to 
>>have two 
>>different versions of each form etc & record many lines of 
>>code to say 
>>"If in postgres add a public. to every table name" which is a 
>>huge pest 
>>& I don't want to have two version of each form to try & keep in sync 
>>with each other.
>>    
>>
>You can't abstract it into a macro or function - i.e. in your forms have
>something like
>
>EXECUTE("SELECT * FROM " + FixName("MyTable"));
>
>(bearing in mind I know nothing about Paradox)?
>  
>
SQL querying in paradox is straight forward. I can just give it the name 
of the table without any schema. It the rest of the interface & data 
models which breaks things when schemas are present in the table names. 
Querying Postgres is quite simple to get working but the data models are 
another story. It's a bloody pest really. Sometimes I wish I knew 
nothing about paradox as well!!

-- 
  Paul Cochrane       (paul(dot)m(dot)cochrane(at)tuht(dot)scot(dot)nhs(dot)uk)
+--------------------------------------------------------
| Tayside Orthopaedic & Rehabilitation Technology Centre
| Ninewells Hospital & Medical School
| Dundee, Scotland, UK.	
| DD1 9SY
| Phone: Internal: 36284
|        External: +44 (1382) 496284
| Fax:   +44 (1382) 496322
+--------------------------------------------------------	


In response to

pgsql-odbc by date

Next:From: Dave PageDate: 2005-02-10 15:42:43
Subject: Re: Compiling using Visual Studio 2003
Previous:From: Dave PageDate: 2005-02-10 14:54:45
Subject: Re: Compiling using Visual Studio 2003

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group