Received: from igwserver.DILIGENCE.COM (www3.diligence.com [206.252.234.248]) by hub.org (8.10.1/8.10.1) with ESMTP id e71LRIB21943 for ; Tue, 1 Aug 2000 17:27:18 -0400 (EDT) Received: from al ([192.168.0.1]) by igwserver.DILIGENCE.COM (Post.Office MTA v3.5.3 release 223 ID# 0-56960U300L2S100V35) with ESMTP id COM for ; Tue, 1 Aug 2000 15:27:27 -0600 Message-Id: <4.2.0.58.20000801152147.00a4c9b0@diligence.com> X-Sender: tim@diligence.com X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58 Date: Tue, 01 Aug 2000 15:27:24 -0600 To: pgsql-interfaces@postgreSQL.org From: Tim Uckun Subject: Linking views and tables to access. In-Reply-To: <398703E5.10395.47F9ACE@localhost> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Archive-Number: 200008/10 Hello. I am having a couple of problems. One is that when I attempt to link SOME tables to access I get an error messages about an index containing a non existing field (an empty string). The other is that when I attempt to link a view as a table I get the following error. ERROR: system column xmin not available - vievname is a view (#1) I strongly suspect that the first error is due to the fact that I changed the NAMEDATALEN in the source when I compiled postgres. I suspect that the ODBC driver is not expecting a large string and is getting one. Could the second problem be related? Also is it possible to compile the ODBC drivers with a similar DEFINE? Right now the NAMEDATALEN is set to 64. Although this is still small compared to access It's a more sane option then 32 for me. :wq Tim Uckun Due Diligence Inc. http://www.diligence.com/ Americas Background Investigation Expert. If your company isn't doing background checks, maybe you haven't considered the risks of a bad hire.