Tom, I just experienced the kind of goofiness you indicate in lookup settings. I believe it was due to my altering a column name after adding it to a table. In other words, adding the column to the table saves without looking in forms but altering the column name runs some internal update routine while saving which may be responsible for this behavior. I haven't had time to recreate and document it for reporting to RDCC.
Can you recall if you altered a table column name before you experienced this behavior? Claudine -----Original Message----- From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of Tom Frederick Sent: Saturday, September 06, 2008 10:38 AM To: RBASE-L Mailing List Subject: [RBASE-L] - DB Lookup ComboBox problems I have two problems with DB ComboBoxes that have me stumped. Using V8 with most recent TimeMachine updates: 1. Lookup Settings will change from Source Table/View to the main Table name for no apparent reason. Example: Form IDInfo has a DB Combo for a city name, table = IDData, data field = "CityName", and compID = CityName. Lookup table = "City", Source Key = CityID, and Column/Where/Order options are set. Run the form and it works as expected for months. Yesterday I worked on tables unrelated to IDInfo. Start going through forms to check for goofy stuff and find all 8 DB Combos in IDInfo no longer work. These DB Combos all use different tables. Simple check shows the Source Tables have all changed to IDData, source key and column are blank, but Where/Orders are set as I left them. Looked at other forms using DB Combos and they are fine. I am the only person with access to the actual form. Fixed everything and it works like always, but the fact the Lookup and Source key changed without me is a puzzler. 2. Cannot get "On Entry" EEP for DB Combos to work. So far all other On Entrys work. Doing an audit system that uses On Entry to set a current field value to a var. If the user changes the field in any way it compares to the var and records the audit data if different. Works fine except for DB Combos where On Entry seems to be ignored. I often use development dummy forms to track code progress. If I put a dummy form or a set var in On Entry, nothing happens. Copy the exact same items elsewhere on the form and they work correctly. Same thing happens in several other DB Combos. Is there something that needs to checked? My next step is to replace the DB combo in case I screwed something up or simply work around the On Entry option. Any ideas for either of these? Tom Frederick Jacksonville Ill.
