Susan Harkins
harkins at iglou.com
Wed Apr 16 10:02:52 CDT 2003
RE: [AccessD] autonumberI understand that -- I'm just saying, there's no reason to use the AutoNumber for this -- almost all of these numbering schemes come from someplace else, not the application -- purchase orders are printed externally -- well, I believe they are in most businesses. I'm saying, the AutoNumber is irrelevant to the function -- it's used by Jet -- not the purchase ordere -- at least it shouldn't be a purchase order number or anything like that. Have I been away from real business for so long that people are printing up their own purchase order forms, etc. using Access?????????????????? I'm just having trouble visualizing this is all. Susan H. ----- Original Message ----- From: Hale, Jim To: 'accessd at databaseadvisors.com' Sent: Wednesday, April 16, 2003 10:46 AM Subject: RE: [AccessD] autonumber <Why would auditors care about the AutoNumber?> It goes back to the old paper days when PO's, invoices, etc were uniquely numbered. For control purposes every copy had to be accounted for. Many software programs carried over this convention from the paper world. If a number is missing from a document series the audit question becomes "what happened to it?." While this may have been a relevant question in paper days it has become less meaningful as accounting software has evolved away from a strict adherence to the paper paradigm. In any case, as JC has pointed out many times, the auto number should remain under the hood. It is database structure stuff with which the user doesn't need to bother himself. The invoice or PO number shown to the user should be handled separately so that database structure remains separate from accounting needs. Jim Hale -----Original Message----- From: Susan Harkins [mailto:harkins at iglou.com] Sent: Wednesday, April 16, 2003 9:27 AM To: accessd at databaseadvisors.com Subject: Re: [AccessD] autonumber Why would auditors care about the AutoNumber? It isn't a purchase number or anything like that... just an internal numbering system. If you use it to create purchase order numbers, well... you might be in trouble, but otherwise, can't see why anyone but the developer would care, even if they can see it. Course, then you get the oddball client that swears you're losing records and won't listen... no matter what you say... Susan H. > Brenda, > > M$ only guarantees that an autonumber will be unique. It does not > guarantee that it will increment by one each time. Users, and > especially auditors, will question you as to why there are gaps in the > numbering scheme. What are you going to say when the auditors ask you > where is the paperwork for the missing numbers? > > Charles Wortz > Software Development Division > Texas Education Agency > 1701 N. Congress Ave > Austin, TX 78701-1494 > 512-463-9493 > CWortz at tea.state.tx.us > > > > -----Original Message----- > From: Reische, Brenda L. [mailto:reische at mdh.org] > Sent: Wednesday 2003 Apr 16 08:12 > To: 'accessd at databaseadvisors.com' > Subject: RE: [AccessD] autonumber > > Charles, > The archives appear to be down right now. Care to enlighten me? I let > the users see the autonumber field. In my ambulance services database, > that is the unique run id number that we use - it prints on the medical > record and > everything... Why is this a cardinal sin? > > Thanks, > Brenda Reische > McDonough District Hospital > > -----Original Message----- > From: Wortz, Charles [mailto:CWortz at tea.state.tx.us] > Sent: Wednesday, April 16, 2003 7:46 AM > To: accessd at databaseadvisors.com > Subject: RE: [AccessD] autonumber > > John, > > I cannot let this pass without asking why do you care? You are not > committing the cardinal sin of allowing you users to see the autonumber > field are you? <grin> If so, check the archives on why this is a > cardinal sin. > > Charles Wortz > Software Development Division > Texas Education Agency > 1701 N. Congress Ave > Austin, TX 78701-1494 > 512-463-9493 > CWortz at tea.state.tx.us > > > > -----Original Message----- > From: Drew Wutka [mailto:DWUTKA at marlow.com] > Sent: Wednesday 2003 Apr 16 05:02 > To: 'AccessD at databaseadvisors.com ' > Subject: RE: [AccessD] autonumber > > A make table query should already 'reset' the AutoNumber, since it is > going to make a new table. An append query can be used to 'set' numbers > within an AutoNumber field, however, it doesn't reset the counter, it > can just 'ignore' it. If you delete the data in a table, to resent the > AutoNumber counter, compact the database. It will reset the counter (on > an incremental > AN) to the highest number plus 1 (or 1, if there are no records > remaining). > > Drew > > -----Original Message----- > From: John Eget > To: AccessD at databaseadvisors.com > Sent: 4/16/03 4:43 AM > Subject: [AccessD] autonumber > > Is there a way to reset the autonumber to 1 of a make table query or an > append or a table I just finished deleting the information from? John > <<ATT46269.txt>> > _______________________________________________ > AccessD mailing list > AccessD at databaseadvisors.com > http://databaseadvisors.com/mailman/listinfo/accessd > Website: http://www.databaseadvisors.com > > _______________________________________________ AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com ------------------------------------------------------------------------------ _______________________________________________ AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://databaseadvisors.com/pipermail/accessd/attachments/20030416/632c4888/attachment-0001.html>