Welcome to SPN

Register and Join the most happening forum of Sikh community & intellectuals from around the world.

Sign Up Now!

How do I prevent #deleted appearing before I update a query?

Discussion in 'Information Technology' started by Rosalind, Jul 28, 2006.

  1. Rosalind

    Rosalind
    Expand Collapse
    Guest

    A database is open by 2 users. The 1 inputs data and the other is used to
    display the data in form view. As soon as data is updated by user 1(owner)
    all fields on the form of user 2 displays #deleted until shift+f9 is pressed.
    How do I prevent #deleted appearing?
     
  2. Loading...

    Similar Threads Forum Date
    How to prevent sikh erosion? Blogs Oct 21, 2015
    Leisure Stomach Protection / Prevention for travelling to India?? Business, Lifestyle & Leisure Oct 18, 2013
    Controversial Panch Pardhani leader arrested; prevented from attending Shaheedi samagam of Bhai Jaspal Singh Hard Talk Mar 30, 2013
    World Women must play greater role in conflict prevention, UN says Breaking News Oct 28, 2011
    Sikh Coalition Bullying Prevention Summit. Register Today! Sikh Organisations Oct 19, 2011

  3. Tom Wickerath

    Tom Wickerath
    Expand Collapse
    Guest

    Hi Rosalind,

    A quick search of the MS Knowledge Base shows that #Deleted is commonly
    associated with having linked ODBC data and not having the latest service
    pack for the JET database engine installed. For example:

    FIX: #DELETED Error When Inserting Records with CHAR Primary Key
    http://support.microsoft.com/kb/264766/en-us

    and

    Access displays #DELETED when you insert data with the same value into a
    non-unique Key column of a remote table
    http://support.microsoft.com/kb/291546/EN-US/

    Do you have the latest service pack for the JET Database Engine installed on
    both PC's? See this article for information on how to deterimine this:

    How to keep a Jet 4.0 database in top working condition
    http://support.microsoft.com/?id=303528

    Also, are you using linked ODBC data?


    Tom Wickerath, Microsoft Access MVP

    http://www.access.qbuilt.com/html/expert_contributors.html
    http://www.access.qbuilt.com/html/search.html
    __________________________________________

    "Rosalind" wrote:

    > A database is open by 2 users. The 1 inputs data and the other is used to
    > display the data in form view. As soon as data is updated by user 1(owner)
    > all fields on the form of user 2 displays #deleted until shift+f9 is pressed.
    > How do I prevent #deleted appearing?
     
  4. Ron2006

    Ron2006
    Expand Collapse
    Guest

    Just to make sure,

    When the first user is "Updating" the table, does it intail deleting
    any or all of the information that the second user is looking at.

    Just making sure, for if it is perhaps a recap table or something like
    that, that is emptied and redone, then #delete will appear and I
    haven't seen anyway of getting around that one.
     
  5. dbahooker@hotmail.com

    dbahooker@hotmail.com
    Expand Collapse
    Guest

    well the problem is that MDB **JUST ISNT RELIABLE ENOUGH** for multiple
    users to use.
    it's not reliable enough for a single record and a single user.

    screw MDB and don't listen to these MDB wimps.
    upgrade your app / db to sql server and utilize access data projects.

    they are 10,000 times more powerful and reliable than silly obsolete
    mdb files
     
  6. Ron2006

    Ron2006
    Expand Collapse
    Guest

    Interesting opinion dbahooker.

    If you feel so strongly then stay away and then anything we say will
    NOT aggrivate you so much.
     
  7. dbahooker@hotmail.com

    dbahooker@hotmail.com
    Expand Collapse
    Guest

    hey screw you buddy

    im not saying access is evil; i use Access every every single day.
    I'll be damned if i am not free to speak my mind in an access newsgroup

    im saying that mdb is for wimps and you assholes need to gtf out of my
    newsgroup

    Access Data Projects throw away most of the crap of MDB but it still
    allows you to preserve a lot of your application logic.

    the difference in performance is extraordinary.
     

Share This Page