Search results

Agreed. Use dynamic querying to do a loop on a variable as tablename.

Yes this is fine code to extract ALL the numbers out of a string. Be careful to use this, for it seems the poster wants to extract a number from a string which seems to be divided in clear fragments. So yes, this code can be used if the poster wants to get "14568" from the following string...

Yes, well... Long live character based and so on.

Whoops, didn't mean to step on anybody's toe there ;). Well, to be honest with you, in our line of business it seems that more and more customers are migrating to windows environments. Not because of any downsides to UNIX, but yes there are not that many UNIX experts compared to windows...

But, correct me if I'm wrong, this is not an answer to the question, or am I missing something? The TS wants to group data based on column values, not just export the records in a comma delimited way.

Hardware mismanagement is excluded; this happened in 4 totally different cases. kill -9 is from the UNIX era isn't it? This all happened in Windows environments. I haven't opened a tech case with Progress yet, 'cause I want to be very sure it has something to do with the conv910. The case right...

Yes that was what I was afraid of... (no storage of metadata). I already made a script that can parse the output but it feels like a workaround (which it really is). I know have to choose between somewhat inaccurate information which is gathered with a workaround, or a really slow tablescan...

Hi, I was wondering; in which table (system) is the dbanalys information stored? I can't seem to find any metadata table and this is by far the fastest way to get tablescan info. Another question regarding the dbanalys command; is the number of records accurate information or index information?

Hi fellow Progress fans, In the last few weeks we had 4 separate cases in which a proutil conv910 leads to (assumably) corrupt indexes and even corrupt database blocks. (9.1E sp4 > OE 101C sp3). Is there an explanation for this and a standard procedure for conv910 which is 100% bullet proof...

That is, by far, the simplest way to do it :)! The FIRST-OF function, however, can not be used in dynamic querying. So if you're going to do things dynamically, the above is not an option. For static querying the above is a very good solution!

Uhm, I would do something like this: /* Creation and filling of temp-table, not of interest for the endresult */ DEFINE VARIABLE htemptable AS HANDLE NO-UNDO. DEFINE VARIABLE hbuftemptable AS HANDLE NO-UNDO. CREATE TEMP-TABLE htemptable. htemptable:ADD-NEW-FIELD("MemberID","integer")...

The statement being dynamic has everything to do with not getting an explicit error. You are right concerning the fact that keywords may or not may used in static and dynamic statements, but if you code statically you get a whole different error (which is a LOT more explicit in my belief)...

Thank you. Are all the keywords in the list not to be used in dynamic statements?

Well Greg, that was very useful! I changed the names to databasename and tablename and things are running smoothly now. Thanks man! I'd surely like to see a list of names NOT to be used in expressions, because they give errors on run-time. Or Progress could give me a better error... Anyway...

Hi, I've created a temp-table htempxmlcolumns containing 4 fields: username, database, table, fields. Then I do some logic and I fire this statement: IF htempxmlcolumns:HAS-RECORDS THEN hbufxmlcolumns:FIND-UNIQUE(SUBSTITUTE("where username = &1 and database = &2 and table =...

Haha, yeah that rings a bell! I always used the 'default-action' trigger :) to select a row. Very useful!

Just for the record: you can use the function QUOTER to handle these kind of things. So '" + vchsitelist + "' would become " + QUOTER(vchcitelist) + "

Thanks! Yeah I needed the Progress side to work, just to be sure the query I used was right. The Oracle thing will be solved!

Hi all, I have a question concerning a query using BREAK BY statements. It takes a relatively long time for the query to hit the first record it seems. The query is: ETIME(YES). FOR EACH debtrs WHERE debtrs.adm-nr = 100 AND debtrs.entry-nr >= 100 AND...

Haha, quite right there Tom.