From: Tim Uckun <tim@diligence.com>
To: pgsql-interfaces@postgresql.org
Subject: Re: Some advice re:bound/unbound forms for MS Access
Date: Thu, 30 Nov 2000 15:02:45 -0700
Message-ID: <4.2.0.58.20001130145840.014a6008@mail.diligence.com> (raw)
In-Reply-To: <3A266829.31508.4FE16D@localhost>
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.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-interfaces@postgresql.org
Cc: tim@diligence.com
Subject: Re: Some advice re:bound/unbound forms for MS Access
In-Reply-To: <4.2.0.58.20001130145840.014a6008@mail.diligence.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox