Received: from diligence.com ([216.166.138.131])
	by mail.postgresql.org (8.11.1/8.11.1) with SMTP id eAUM2OF18854
	for <pgsql-interfaces@postgresql.org>;
	Thu, 30 Nov 2000 17:02:25 -0500 (EST)
	(envelope-from tim@diligence.com)
Received: (qmail 1450 invoked from network); 30 Nov 2000 22:05:04 -0000
Received: from unknown (HELO ddi-kl3f5lagj0p) (192.168.0.54)
	by pdc.diligence.com with SMTP; 30 Nov 2000 22:05:04 -0000
Message-Id: <4.2.0.58.20001130145840.014a6008@mail.diligence.com>
X-Sender: tuckun@mail.diligence.com
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58 
Date: Thu, 30 Nov 2000 15:02:45 -0700
To: pgsql-interfaces@postgresql.org
From: Tim Uckun <tim@diligence.com>
Subject: Re: Some advice re:bound/unbound forms for MS
  Access
In-Reply-To: <3A266829.31508.4FE16D@localhost>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Archive-Number: 200011/299
X-Sequence-Number: 336

At 02:46 PM 11/30/2000 -0500, Joel Burton wrote:

>[Warning! VisualBasic code ahead. If this offends your religious
>sensibilities, skip to the next message. :-) ]

Thanks for the tips.

Maybe this method can be used with ms-sql server too. It has some very nice 
error messages like "overflow" or "ODBC Call failed" or "Invalid operation" 
of course it couldn't bother to tell me anything else. Both Access and SQL 
server have horrible error messages. May favorite is "there is no message 
for this error".


: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.