|
That's the conclusion I am coming too (e.g. there is no "elegant", quick solution). Had thought of the first one but these 500 queries are used in 550 different lines of CL (probably around 150-200 CL's) so changing them for either of your solutions isn't a whole lot faster (oh, did I mention I need to get this done before 7 pm tonight!!!!) than just putting 2's beside them in wrk qry then F3 and on to the next, the next, the next...... But thanks for your input, I'll let you know if anyone else gives me a miracle...... Mark Allen IS Manager Kelly's Kids markallen@kellyskids.com -----Original Message----- From: owner-midrange-l@midrange.com [mailto:owner-midrange-l@midrange.com]On Behalf Of Reger, Bill Sent: Tuesday, February 01, 2000 1:07 PM To: 'MIDRANGE-L@midrange.com' Subject: RE: ? regarding Queries Mark, A couple of suggestions (none great). 1. Issue an OVRDBF command with LVLCHK(*NO) prior to executing a query OR 2. Retrieve the equivalent QMQRY source and then create the QMQRY object from that source. * RTVQMQRY with ALWQRYDFN(*YES) * CRTQMQRY from the retrieved source to create the QMQRY * STRQMQRY to execute the QMQRY William K. Reger Senior Project Manager Levitz Furniture Corporation Phone: (561) 994-5114 E-mail: breger@levitz.com <mailto:breger@levitz.com> -----Original Message----- From: Mark Allen [mailto:markallen@kellyskids.com] Sent: Tuesday, February 01, 2000 11:24 AM To: 'MIDRANGE-L Subject: ? regarding Queries We recently added fields to one of our "Master" files. All is well except for queries that run against that file, they are erroring out (i.e. equivalent to a level check). The only way I know of to fix is to WRKQRY on that query with revise and exit. that works fine except I have 500+ queries that use the file (DON'T ASK!!!!). Does anyone know of a way to do a batch type update, or at least some automated way to correct????? Mark Allen IS Manager Kelly's Kids markallen@kellyskids.com +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@midrange.com. | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +--- +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@midrange.com. | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +--- +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@midrange.com. | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +---
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.