-===> Quoting Bill Cheek to Jim Chevraux <=-
 BC> Right.  That's where Cindy and I begin to lose contact with reality 
 BC> and the hard ground.  Code......  &*%%$#*
        Heh, I know the feeling ... I get that way frequently.  Have to take 
mental leave from my job, lose pay, have to put up with the shrink......  :-)
 BC> Cindy is hung up on details while I am hung up on the broader view, 
 BC> but neither of us can get very far at times.  Me, I can see the clear
        First things first ... work on the detail first ... in this case, how 
to accomplish what you're trying to do in a specific case.  Pick one field, 
that when updated, will make the [Modified] field's contents change to 
reflect 
the current date.  Once you've got that down, you're halfway there.  You've 
discovered HOW to accomplish what you're doing in one case.
        Then go for the broad view ... how to best accomplish that same thing 
(that you now know how to do with code) whenever ANY field is modified.  In 
this case, best I can suggest is to do the same thing with each field on the 
form.  I don't know of any way to do this in one stroke.
 BC> On that note, can you recommend a STARTING POINT from which to pick 
 BC> this stuff up and learn it?  Between the two of us, Cindy and I know
        First, find yourself a good reference book on Access Basic.  
Personally, I'd recommend the Access Developer's Toolkit.  It comes with a 
nicely done manual that gives you full reference to all code.  However, it's 
pretty expensive, since that's not just a reference manual.  You may want to 
find a third-party reference of some sort.
        Second, check out the sample databases that come with Access.  They 
contain all kinds of code.  If you play around with the database, you may 
very 
well find a case where it's doing something at least similar to what you're 
trying to do.  Then start poking around in it to find out HOW it's doing it.
 BC> We can emulate; simulate; replicate; theorize; hypothesize; and 
 BC> synthesize; but we can't get to first base on our own...not without a
        Exactly what the latter part of my recommendation gets you into.  It 
gives you specific code, where you can play with the database and see the 
exact results of the code.  Keep two copies ... one that you don't change, 
and 
another that you do change.  Modify the code a little here and there while 
trying to learn how a particular piece of code works.  Then go back into the 
form or whatever and see how your changes affected the way the form works.
jc
 
... Hell must be full, the damned are working in tech support
--- FLAME v1.1
---------------