John, Why not apply your logic below as the data is entered? That way you don't have to be concerned about it downstream, and probably don't need the computed columns.
Emmitt Dove Manager, DairyPak Business Systems Evergreen Packaging, Inc. [EMAIL PROTECTED] [EMAIL PROTECTED] (203) 643-8022 -----Original Message----- From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of John Docherty Sent: Monday, February 11, 2008 2:45 PM To: RBASE-L Mailing List Subject: [RBASE-L] - Re: DB LookupListBox Error Mike, Thanks for your reply. The reason for the computed columns being used is as follows:- The database is being used for the preparation of tenders. The items being priced are described in various ways by different consultants who supply schedules (SCHED table) to be priced. In addition the descriptions can be typed in manually, or selected from a list. The use of the computed columns was to remove extraneous spaces, abbreviations and the like from the description and then to allow that to be compared to the 'standard' description in a RATES table. The computed columns are:- de4=(SRPL(SRPL(SRPL(SRPL(de,'mm ','',0),' ','',0),'dia','',0),',','',0)) de5=(ULC(SRPL((SRPL(de4,'-','',0)),'extravaluefor','',0))) I also used hashed columns to try to speed up the matching. I was using de5 as the link between the SCHED and RATES table, with the SCHED table in a dbgrid and the RATES in a DBLookupListBox when there was a match the row in the ListBox was automatically highlighted, you clicked on the Listbox and the SCHED table was updated with the RATES information. (This was just one means of updating and inserting data, but the beauty of the listbox was that it would display additional information such as the date of the last price and the supplier etc.) This has worked well for at least two years, allowing hundreds of jobs to be priced, and has only produced the error recently. Obviously I am in for a bit of a rethink on how best to do this - I would appreciate any suggestions that you may have that would allow me to accomplish what I have been doing. Thank you. Regards, John Docherty -----Original Message----- From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of MikeB Sent: Tuesday, 12 February 2008 1:36 a.m. To: RBASE-L Mailing List Subject: [RBASE-L] - Re: DB LookupListBox Error I for one would like to see you dispense with the computed on computed arrangement, even if it is for the sake of clarity. I think you said that is different from when you Weren't having any trouble with an earlier version. I honestly can't think of the last time I used a computed column. I am sure I may use one yet, but It just hasn't happened. I tend to think in terms that data is data and any thing after that is manipulation or presentation, with either scenario pretty much able to be done on the fly at runtime. ----- Original Message ----- From: "John Docherty" <[EMAIL PROTECTED]> To: "RBASE-L Mailing List" <[email protected]> Sent: Monday, February 11, 2008 12:54 AM Subject: [RBASE-L] - Re: DB LookupListBox Error Razzak, Thanks for your replies. I will do as you have suggested and will let you know what I find. To answer your easy questions though, the column in question is a computed column, (on a computed column - perhaps not the most elegant solution) and I could change it using Data Designer to match the definition in another table, but the form isn't trying to change it at all it just links the two tables. (I had sent the sample earlier though so I hope I am not wasting anyone's time - the fact that this worked earlier with 7.5 and doesn't now just suggests that something has changed, or maybe that what I could 'get away with' in earlier versions is not possible now.) Thank you. Regards, John Docherty -----Original Message----- From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of A. Razzak Memon Sent: Monday, 11 February 2008 5:53 p.m. To: RBASE-L Mailing List Subject: [RBASE-L] - Re: DB LookupListBox Error At 04:23 AM 2/10/2008, John Docherty wrote: >I have a DBLookupListBox which has worked previously without >problems, however I now get an unnumbered error message stating >"Field de5 cannot be modified" when I click on an item in the >list. de5 is the data field (column), from a view, specified in >the listbox property. John, Have you changed the definition of the "de5" column? Is it a "Computed" column? If the "de5" is a computed column, you cannot update/modify the computed column. Forcing to update the computed column using DB Edit control in a form will result in that -ERROR- message. FYI, computed column(s) are updated automatically. Very Best R:egards, Razzak.
