We use a pay-per-click service from www.postcodeanywhere.co.uk for the
postcode validation - very simple to access using U2's callhttp
functions, and cost effective for the sorts of volumes we use.
Hope this helps,
Simon
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL
I've just acquired another client who's system doesn't use READU (sic) but
uses LOCK then UNLOCK to surround the READ and WRITE statements. They have a
table to assign the LOCK numbers to specific files but it seems incredibly
overkill.
Does anyone else have this kind of setup and can offer some
Mark,
I may be wrong, but I have a vague memory that in the very early days,
multivalue databases (Pick?) didn't have record level locking.
Use of LOCK/UNLOCK is hard to justify and probably even harder to get to
work without endless deadlocks. I came across a legacy application recently
that
I recall back in the early EARLY 80s working on a version of Pick (cannot
remember which though!) that did not have any implicit locking at all on
READs or WRITEs, only the LOCK / UNLOCK mechanism. We had a header file of
assigned LOCKs that we included everywhere so others could figure out what
In a message dated 7/5/2004 7:04:08 AM Pacific Daylight Time,
[EMAIL PROTECTED] writes:
I may be wrong, but I have a vague memory that in the very early days,
multivalue databases (Pick?) didn't have record level locking.
Martin you are not wrong. And it wasn't the very early days :) Well
In the early days, it was group locking rather than record locking.
However, this technique locks the entire file.
Eugene
- Original Message -
From: Martin Phillips [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Monday, July 05, 2004 7:39 AM
Subject: Re: [U2] READU vs LOCK
Mark,
I
From: Mark Johnson
Not for nothin' but there are some pretty ugly I-type dict
items with all the SUBS, EQS, REUSE etc stuff.
Before I disagree with some points, let me concur that I-types'
MV-handling can be ugly.
Although Prime traded the ugly correlative syntax for the inherent
simplicity
You are both on the right track.
I may be wrong, but I have a vague memory that in the very early days,
multivalue databases (Pick?) didn't have record level locking.
Martin you are not wrong. And it wasn't the very early days :) Well maybe
it was and I'm just a dinosaur ...
It was the early
