Leland,
thanks for having pointed me to a direction where I discover a lot
of interesting things. What I *think* I have learned from it is that what
I'm trying to do is doable. I did some steps forward, though, as I'm writing
answering to Matthew's post.
Iames
-----Messaggio originale-----
Da: [email protected] [mailto:[email protected]] Per conto di
Leland Jackson
Inviato: martedì 14 dicembre 2010 14:48
A: ProFox Email List
Oggetto: Re: VFP 9.0 SP2: problem connecting to PostgreSQL 8.3.4 on Debian
4.1.1 (32 bit)
#------------------------------
Excerpt:
Windows version-specific issues
Can I install a 32-bit PostgreSQL on 64-bit Windows?
Recent 32-bit versions of PostgreSQL (8.3 and newer) can be installed and
used on 64-bit Windows XP and above, though they retain the 32-bit limits on
maximum process address space (and thus shared memory).
You can connect to the 32-bit postgresql server from 64-bit programs on the
computer the server is running on or other computers if a 64-bit libpq or
psqlODBC driver is installed where the program is running.
Because 32-bit versions of the PostgreSQL server only install a 32-bit libpq
and pgsqlODBC, only 32-bit programs on the computer the server was installed
on can use the database unless a 64-bit ODBC driver or libpq is installed as
an add-on.
Where is the PostgreSQL ODBC driver? I'm running 32-bit PostgreSQL on 64-bit
Windows
You need to use the 32-bit ODBC administrator to set up data sources for
32-bit applications using 32-bit drivers.
Unless you've also installed a 64-bit version of psqlODBC, a 32-bit install
of PostgreSQL will only have a 32-bit ODBC driver. The 32-bit ODBC driver
may only be used by 32-bit programs, and will not show up in the 64-bit ODBC
administrator.
This gets confusing because on 64-bit windows
c:\windows\system32\odbcad32 is the 64-bit ODBC driver administrator,
despite the name. This is a historical artifact of Windows development.
Apparently many apps and installers depend on odbcad32.exe having that name
and path, so Microsoft landed up being stuck with it despite the now-stupid
name, which made sense back in the 16- to 32-bit transition but makes none
now. It's the same reason the "system32" directory is still called that on
64-bit Windows. PostgreSQL can't do anything about this.
See: http://support.microsoft.com/kb/942976
You'll see in that article that the 32-bit ODBC administrator on 64-bit
Windows is:
%systemdrive%\Windows\SysWoW64\odbcad32.exe
You can launch this from "Start->Run" using the path above. You will see the
PostgreSQL ODBC drivers in the 32-bit ODBC administrator.
You 'can not' use a 32-bit ODBC driver in a 64-bit application. That means
that you'll still only be able to use the PostgreSQL ODBC driver with 32-bit
applications unless you install a 64-bit ODBC driver as well.
Can I use a 64-bit ODBC program with a 32-bit PostgreSQL server?
Only if you have a 64-bit [1] driver installed. See the installation
section.
http://wiki.postgresql.org/wiki/Running_&_Installing_PostgreSQL_On_Native_Wi
ndows
#-------------------------------
_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://leafe.com/mailman/listinfo/profox
OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message:
http://leafe.com/archives/byMID/profox/[email protected]
** All postings, unless explicitly stated otherwise, are the opinions of the
author, and do not constitute legal or medical advice. This statement is added
to the messages for those lawyers who are too stupid to see the obvious.
