Search results

Right, one of the principles of good ABL programming is to figure out what needs changing without opening a database transaction and then to open, apply, and close in the shortest possible time. If you do that, then the problem goes away.

Note also that your examples 1 and 2 do not show any scoping. Any update should be done in a strongly scoped block.

For future reference, stick this URL in your reference file for code page issues. Internationalization (I18n), Localization (L10n), Standards, and Amusements

If this is just a display, there is no reason for any locks, so all of your reads should be no-lock.

As discussed on Progress Communities, the issue here is trying to mix positional and named parameters. Once you use a named parameter, positional parameters cannot be used.

Presumably, the obstacle to install is human, not technical ...

BTW, you might want to add Internationalization (I18n), Localization (L10n), Standards, and Amusements to your bookmarks for a lot of information on this topic.

Depending on the need, you could move to an extended code page like UTF-8 that is more likely to have a superset of the characters you want, but that is a non-trivial commitment. So, you need to ask yourself why you need any particular character and how important is it to the application. If...

The table you are showing is not for 8859-1 ISO/IEC 8859-1 - Wikipedia There is no box in 8859-1.

Plus -n has only a passing relationship to licensing ...

For situations like this, my inclination is to test the values the user has supplied and construct a where clause dynamically based on what I find there. Thus, if the user supplies "*", simply omit that field from the where clause altogether. Not only does this allow making much more efficient...

Done the COMPILE LISTING yet? You can also do it for the program that calls this one to see if there is a transaction active at the time of the call. Other than that, I agree with the other advice you have been given. Sometimes, people think they need huge transactions out of some notion that...

Replace() is a much faster way.

The two common ways of looking at the data are an ABL program (the Progress 4GL) or SQL. But, given your apparent lack of ABL knowledge (or you wouldn't be asking the question), a third option, as Marco suggests, is DataDigger, which is ABL designed to make it easy to browse through the data...

I.e., code it the way you should and the issue doesn't arise ... :)

So that it can be used. If it is inactive, it can't be used.

You don't want *any* number separator except the decimal when providing numeric constants.

Are we talking about using persistent or superprocedures?

To followup on what James said, good progress implies encapsulation of related behavior in a procedure or object and clear passing of needed parameters between these procedures or objects, so that you can clearly trace the flow of information and know exactly where something came from and went...

RECORD-LENGTH gives you the size of the *data* in the record. On disk there is additional space consumed by the DB housekeeping information.