Hi, Vernon. I'm afraid I'm going to start sounding like an annoying
nag. :-) If you really want help with this project, you need to meet
me half way. If you're swamped with work right now, please at least
write back and say something like "I'm buried under a project right
now, and I won't be able t
[ Having a conversation with myself again :-) ]
It looks as if the second problem I reported with the Access suite is
a result of one of my patches. Apparently with the patch Access (but
not SQL Server) treats binary values incorrectly (at least sometimes).
Without the patch, SQL Server is unable
Ummm ... "I'm buried under a project right now, and I won't be able to get
back to you until next Friday." My day job has been burning up a lot of
time, and we had an important Family Occasion on Saturday that ate the
entire weekend. Sorry. I will try to do better at context switching.
You are he
On Wed, Feb 21, 2018 at 12:04 PM, Vernon D. Cole wrote:
> Ummm ... "I'm buried under a project right now, and I won't be able to get
> back to you until next Friday."
No worries. I'll keep plugging along with getting my test bed
assembled and then hold off until you come up for air.
Thanks,
Bob
On Wed, Feb 21, 2018 at 10:26 AM, Bob Kline wrote:
> Without the patch, SQL Server is unable to store a NULL value or an
> empty string properly using placeholders. So we need to find out why
> that is, and come up with a version of the patch which fixes the
> second problem in SQL Server without
