Received: from smtp-out2.bellatlantic.net (smtp-out2.bellatlantic.net [199.45.39.157]) by hub.org (8.9.3/8.9.3) with ESMTP id OAA13254; Mon, 20 Dec 1999 14:41:39 -0500 (EST) (envelope-from daybee@bellatlantic.net) Received: from bellatlantic.net (client196-126-40.bellatlantic.net [151.196.126.40]) by smtp-out2.bellatlantic.net (8.9.1/8.9.1) with ESMTP id OAB20182; Mon, 20 Dec 1999 14:47:33 -0500 (EST) Sender: dchartwig@bellatlantic.net Message-ID: <385E874F.C8398C52@bellatlantic.net> Date: Mon, 20 Dec 1999 14:45:19 -0500 From: David C Hartwig Jr Organization: Sonnet Software, Inc. X-Mailer: Mozilla 4.51C-Caldera [en] (X11; I; Linux 2.2.5 i686) X-Accept-Language: en MIME-Version: 1.0 To: Michael Meskes CC: PostgreSQL Interfaces Subject: Re: [INTERFACES] Access problems References: <19991220152353.A585@fam-meskes.de> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Michael Meskes wrote: > I have installed onshore-timesheet on my machine. It works like a char. No I > tried to access the database via M$ Access and found some problems. The ODBC > connection is up and running. However, Access refuses to link in several > tables. > > I attach the table definitions. > > It says the following attributes are not correct either in index or in > relationship definition: > > table attribute > ------------------------------- > category category_id > hours del > job downloaded > notification fkpersonnel_id > personnel personnel_id > > Only the client relation is okay. > > So far I wasn't able to see what's wrong with these. Maybe anyone on this > list has an idea. Also ODBC logs don't show something special. > > I am a bit rusty on the internals on the psqlODBC driver as it relates to MS Access. But as I seem to recall, Access cannot have a key column over 256 bytes. Text columns are virtually unbounded. This may explain some of your tables linking problems. If you can, try changing some of those primary key fields to varchar(255) or smaller. Ultimately what you need to do is activate the logging feature in the driver and attach a minimalist failure log file.