Results 1 to 3 of 3
  1. #1
    2 Star Lounger
    Join Date
    Oct 2001
    Location
    Canberra, Australian Capital Territory, Australia
    Posts
    136
    Thanks
    0
    Thanked 0 Times in 0 Posts

    USys_SwapTable (Access 97)

    <P ID="edit" class=small>(Edited by browningj on 14-Jan-04 06:48. I should have included the field from the query to explain a bit more. The query contains a calculated field containing the following:
    NameCard: IIf([Field1]=True,[Name Card 1],[Name Card 2])
    Field1 comes from USys_SwapTable, and Name Card 1 and Name Card 2 come from another table
    )</P>Hello Access Gurus,

    I have just come across a database that uses a USys_SwapTable. Can anyone explain what this table does? I can see that it contains a Yes/No field but when it is used in context with a query that displays results from 2 tables it appears to generate two occurrences of the same record depending on whether the value is Yes or No. I am wondering also where it gets its values from.

    I look forward to your response here.

    Cheers,

    Jocelyn

  2. #2
    Plutonium Lounger
    Join Date
    Dec 2000
    Location
    Sacramento, California, USA
    Posts
    16,775
    Thanks
    0
    Thanked 1 Time in 1 Post

    Re: USys_SwapTable (Access 97)

    Any table named USys anything is a user-defined system table. That means it behaves like a system table but it is not one of the built-in tables. That means that no one can explain anything about it or what it does because those characteristics are contained in your database.
    Charlotte

  3. #3
    Super Moderator
    Join Date
    Aug 2001
    Location
    Evergreen, CO, USA
    Posts
    6,624
    Thanks
    3
    Thanked 60 Times in 60 Posts

    Re: USys_SwapTable (Access 97)

    It presumably is something a developer created that they didn't want to be readily visible to users - it's a trick we use sometimes. If you name a table uSysXXXXX, it isn't visible in the database window unless you turn on the options flag that lets you view system tables. In this case you might want to do that to see if there is any description of the table in it's properties, and look at it from a design view to see if any info has been included on fields and how they are used.
    Wendell

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •