[AccessD] Membership File Changes

Bill,

<<
>> .  If you reset the seed value of an AN to the max value of a long, the
next number
assigned will be negative, thus invalidating your check>>

... and who in their right mind would do this? As you wrote, ".  I've never
seen anyone do it, yet""
>>

<<
Well that's your prerogative, sir! I take a different view entirely, and it
is because adding records in a batch operation, I will often stamp them all
with the same date/time.
>>

 I guess the point is that AN's are not under your control.  It's something
that JET gets it's fingers in and is in control of.  Given that, it doesn't
seem wise to use them.  If I really wanted to ensure that I knew the exact
sequence records were entered in, then I would assign my own sequential
number.  Part of the reason for that is that by saying you consider the
sequence a piece of information, then the AN field is no longer meaningless.


 But I would not be relying on the AN's for sequence because over the years,
time and time again there have been problems with them.

Jim.



-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Bill Benson
Sent: Friday, March 07, 2014 10:23 AM
To: 'Access Developers discussion and problem solving'
Subject: Re: [AccessD] Membership File Changes

I can tell you are not sure.

<<snip>>