An old form name that comes back

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • jaad
    New Member
    • Oct 2009
    • 158

    An old form name that comes back

    Ok, I am confused with something unusual that I have never encountered before.
    I picked up a sample inventory database online and integrated it into my database as a module. Everything worked fine.

    The thing that I am having trouble with is this:
    I renamed a form that used to be called: Transaction list

    I use this form twice as sub-form in two different place and gave it two different names: PurchaseTransac tionDetails and InventoryDeploy mentDetails.
    Worked great and I was happy.

    After a while and after many new entries with new inventory items I started to get a longggggg list of Inventory Items and it was time to shrink or filter this combo box so it would only show the inventory items that are part of a certain Category.

    So I created a dynamic combobox InventoryItem with a category filter query as its control source.

    So when it was time to go into the Expression Building to pick up a reference address to paste under my category field in my qbe query I noticed that the address that I pasted had changed into the original name of what the form used to be called “Transaction List.” How is that possible?

    Expression Builder clearly show the form as being “PurchaseTransa ctionDetail” but when I paste it into my query it changes into “Transaction list”????????? and obviously creates problems when I click the category field in my form.
    Any ideas?
  • jaad
    New Member
    • Oct 2009
    • 158

    #2
    Adendum:

    I've managed to somehow make one of the subform with the dynamic combo box work. don't ask me how this is possible because the reference refers to a form that doesn't exist anymore but it works nevertheless. I've gone line by line to try to reproduce what I did in one of the sub form and it doesn't work. I should have became a mechanic! #&@%!!!!!

    Comment

    • missinglinq
      Recognized Expert Specialist
      • Nov 2006
      • 3533

      #3
      This is a problem that we hear about, from time to time. The answer, I believe, is to import all objects into a new, blank database, delete the old db, then rename the new one to the original name.

      Linq ;0)>

      Comment

      Working...