Ralph: I use Access 2000 but I believe that the approach would be the same in Access 97.
The following would be my suggestion: 1 - Define the individual fields in the table. I assume that you have already done this. As an example, let's call them A, B, and C. 2 - Define an index (Icon is located on the toolbar in table design and looks like a lightening rod) to consist of fields A, B and C in the proper sequence. Do this by giving the index a name (first column) and then defining the fields in the order you want. Once you've defined the index, click on the index name (first column) and select "yes" for Unique from the dropdown list. Please feel free to email me off list if you need more information. Hope this helps. Carol Warman Computers Were Us, Inc. [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> __________________________________________________ > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On > Behalf Of [EMAIL PROTECTED] > Sent: Friday, February 08, 2002 11:19 AM > To: [EMAIL PROTECTED] > Subject: PCWorks: Any Access97 gurus on the list??? > > > To one and all, > > If there are any Access97 gurus on the list, I have a problem with table > definitions that I can not seem to find an answer to. > > In most programming languages, such as Cobol, Assembler, C, C++, > and on and > on, you can define a high level label, and then define subfields that make > up that high-level definition. > > For example, you have a reference value that consist of a letter, number, > and suffix - any of the subitems can appear in multiple > references, so none > are unique. BUT when combined together, the result is a totally unique > reference that can NOT appear more than once. In other words, NO dups. > > HOWEVER, I have not found anywhere where in Access97 how to do > this kind of > field definition - so you can define a table with a reference field, that > is made up of 2 or 3 subfields within the same table. So when a user is > inputing data, each field is not unique BUT when all are combined to make > the reference field, the reference field is defined as indexed > and no dups. > > I have looked in any number of Access97 reference books BUT have not had > any luck finding out how you can do this type of operation, if at all - > maybe I am just not looking at the right index entry in the back of the > books. > > IF you can NOT do this kind of operation within a table, what IS the best > way of approching this operation??? I could do this without any problem in > any number of programming languages that I have worked in in the past. BUT > trying to do this type of definition and operation work in Access escapes > me. > > Ralph ============= PCWorks Mailing List ================= Don't see your post? Check our posting guidelines & make sure you've followed proper posting procedures, http://pcworkers.com/rules.htm Contact list owner <[EMAIL PROTECTED]> Unsubscribing and other changes: http://pcworkers.com =====================================================
