Changing to a user with limited privileges didn't help. I was able to mess around with the pgsqlODBC dialogue a little and got a different error when trying to connect of "connectivity error: Unexpected protocol character during authentication", so I'm thinking VFP8 is sending some SQL_ASCII character that is being changed under the UTF8 encoding, since UTF8 supports all characters of the different languages. I googled around a little on this problem, and a few people have also experienced this and were able to shed some light on it in their web discussions. I'm thinking I will probably need to change the PostgreSQL database back to SQL_ASCII encoding, but who knows. When I get some time I'll give it a try and let you know how it goes.
Regards, LelandJ Leland F. Jackson, CPA wrote: > Yep, I'm running the VFP8 application in windows under an > administrator's account, so I'll switch to a user with limited > permissions and see if that helps. Still, I'm not sure what that would > have to do with an encoding mismatch between VFP8 and PostgreSQL. > > I think I made a mistake when installing PostgreSQL 8.2. First I > uninstalled 8.1. Then I tried installing 8.2 using the Administrator's > account. I never could get it to install. It would copy the files to > the C:\Program Files\PostgreSQL\8.2 directory, but the install script > was never able to set permissions on the directory or files, and would > always roll back. I tried to add a user 'postgres', but the system > indicate that user postgres was already added, but user postgres never > shows up in any of the dialogues under the "user" area of the Control > Panel, so there was no way to see the properties or delete user postgres. > > I tried installing PostgreSQL 8.2 under several directories, but it > always failed when trying to set permissions on directories and files, > and the directories left behind after the .msi rollback would always be > locked, so even as Administer I'm unable to read, write, rename, delete, > etc these directories and whatever might be in them. > > I finally when back to PostgreSQL 8.1, and when reinstalling it, it gave > a message about I should install under a user with limited privileges, > so that what I did. Uninstalled 8.1 and tried installing 8.2 under a > user with limited privileges, but had the same problem with the install > script not being able to set permissions on the files and directories. > Finally went back to PostgreSQL 8.1. Then I discovered the problem of > client encoding mismatch when trying to connect to PostgreSQLfrom a VFP8 > client. > > Regards, > > LelandJ > > > mrgmhale wrote: > >> Hmmmm.... I am using PostgreSQL v-8.1, and in two of my databases I am >> using UTF8, although my main database is ASCII-SQL. I have had no problem >> whatever hitting the PostgreSQL tables with updateable views via ODBC. When >> I alter the table contents, then fire a commit, the changes are applied >> quickly. I am, however, running VFP9 (I never really did much with VFP8) >> for my applications and test environments. I do not see how that could be >> the difference. I am assuming you are not trying to connect to PostgreSQL >> after logging onto Windows as "administrator". Apparently that is not >> allowed. >> >> Sorry I could not be of more help, other than affirming that VFP ought to >> work just fine with UTF8 against PostgreSQL. I am still flogging my way >> through the world of PostgreSQL. But every time I use it I find more >> reasons to appreciate and enjoy it. >> >> BTW, I found the recently released PostgreSQL For Windows book (I got it >> from Amazon) to be an excellent resource. Not quite as good as "A Hacker's >> Guide To VFP6/7", but quite excellent in its own right. >> >> >> Regards, >> >> Gil >> >> >> >> >>> -----Original Message----- >>> From: [EMAIL PROTECTED] >>> [mailto:[EMAIL PROTECTED] Behalf Of Leland F. Jackson, CPA >>> Sent: Monday, April 30, 2007 3:23 PM >>> To: [EMAIL PROTECTED] >>> Subject: VFP to PostgreSQL connection >>> >>> >>> As of PostgreSQL version 8.1, I'm no longer able to connect to a >>> PostgreSQL database that uses encoding UTF8, previously encoding >>> Unicode, from a VFP8 client. Has anyone else hit this problem? Has >>> this problem been address in VFP9? >>> >>> The error message is "client encoding mismatch" which is probably caused >>> by VFP8 not supporting UTF8 encoding. About all I can do with an ALTER >>> DATABASE command is change the name of the database. >>> >>> I could do a pg_dump backup of the UTF8 PostgreSQL database, then DROP >>> it, and then create a ASCII database, and then restore from the >>> pg_dump. Anyone else hit up against this problem, or know if this will >>> work, or know of a better suggestion. >>> >>> Regards, >>> >>> LelandJ >>> >>> >>> >>> [excessive quoting removed by server] _______________________________________________ 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.
