Results 1 to 2 of 2

Thread: Blank records - Navigating and Datacombo

  1. #1

    Thread Starter
    Lively Member
    Join Date
    Oct 2000
    Posts
    98

    Angry

    Visual Basic 6.0
    MS Access 97
    db name: expense.mdb
    table name : dates and times

    First question:
    In my Access table I have no fields that are related
    I have a Telephone number and address
    If the address is 60 records and the telephone num is 50 records; then everytime i add a new record for telephone the record will only appear in the table ten lines down due to the fact that the address field is 60 records....

    I am trying to display a datacombo (presently by using the data environment; I want to change this) i display the records for that field in the list but at the end of the list there all the blank records... HOW CAN I ELIMNATE THIS?

    VERY DESPERATE...


    Secodn problem can most likely be resolved by ficing the first problem:

    Second problem is I am navigating through a db with the following code:

    With rsemps
    .MoveNext
    If .EOF Then .MoveLast
    End With
    ShowData

    This allows me to go formward but when I get to the blank fields it stays on that last record and goes no where..

    HOW CAN I FIX THIS?

    Third problem:

    How can I prevent a user from entering duplicate records??


    Please provide sample code if possible


    ALL HELP IS GREATLY APPRECIATED!


    Steve

  2. #2
    Fanatic Member
    Join Date
    Oct 2000
    Location
    London
    Posts
    1,008
    I don't entirely understand your question - are you displaying records in a grid?

    If the address is 60 records and the telephone num is 50 records; then everytime i add a new record for telephone the record will only appear in the table ten lines down due to the fact that the address field is 60 records....
    I don't get that at all!

    I think you're problem is largely related to design. Whay aren't the tel.# and address related in some formal way?

    In terms of stopping duplicates, you need to define a primary key on the table (or enforce a check in code).

    A better design would solve most of your problems. Some code might be helpful...

    Cheers,

    Paul.
    Not nearly so tired now...

    Haven't been around much so be gentle...

Posting Permissions

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



Click Here to Expand Forum to Full Width