Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Search results for query: *

  1. dbdave

    Cascaded delete... =Could not updae:record locked

    Thanks sko. Not sure why the relationship reverses your mock-up. I have tried the query approach but I run into strife. If you are interested, this is my dilema in detail... I am running a linked data set (tables) to front end UI(forms). I am currently using 2 tables (plus many others) to...
  2. dbdave

    Cascaded delete... =Could not updae:record locked

    Yes you are correct, the '_1' extension you refer to is as a result of Table1 being added to the relationship window a second time. And yes there is a self join from ID to SubID with forced referential integrity and cascaded delete. What I am pinning my hopes on is the fact that Access...
  3. dbdave

    Retro Filling Blank Cells

    I vote for joe's solution... simply and less prone to typo's.
  4. dbdave

    Cascaded delete... =Could not updae:record locked

    Thanks.... I have a suspicion that what you say is correct, but I am bewilderd why everything, including cascaded deletes, works OK before the database is saved for the first time. I may not have made it clear that the table in question has a second field/column that is the subordinate to the...
  5. dbdave

    Cascaded delete... =Could not updae:record locked

    Just adding the finishing touches to a 12 months project and am getting hung up with a persistent error message. I need to run with referential integrity so I can use cascaded delete on a single table, but get this persistent 'locking' problem after I save the database and reopen it. In...

Part and Inventory Search

Back
Top