I'm a home bound quadriplegic that started around fox pro 3.0 or so. I run my living-room/house off snippets of code all of you provide for me. Today I'm trying to figure out VM ware in order to get my 64 bit computer to talk to a 16-bit gadget (and of course) through fox pro. Many of the answers you guys give me go over my head but as I progress, they seem to mean more and more. When Ted answers a question of mine, I feel like Moses with some new commandments.... long drawn out ... thank you, all of you, for your help.
Gary Jeurink -----Original Message----- From: Ted Roche [mailto:tedro...@gmail.com] Sent: Wednesday, April 24, 2013 9:56 PM To: profox@leafe.com Subject: Re: primary or unique index On Wed, Apr 24, 2013 at 10:53 PM, Gary Jeurink <g.jeur...@charter.net>wrote: > > At the point where I generate the billing, the index I want in place would > not allow an insert command to duplicate a billing for that > student/class/session. I just assumed unique meant only 1 allowed per > table. > > It's a common misunderstanding. CANDIDATE and PRIMARY keys only allow unique values. UNIQUE are an old remnant of a quirky FoxPro behavior and should NEVER be used. -- Ted Roche Ted Roche & Associates, LLC http://www.tedroche.com --- StripMime Report -- processed MIME parts --- multipart/alternative text/plain (text body -- kept) text/html --- _______________________________________________ Post Messages to: ProFox@leafe.com Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/E22D4B5B72034E9BA1ABDB1D1253F618@OwnerPC ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
