Search results

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.

For each?

If you F4 within a transaction, it will roll back. So, don't do that. You need to either limit the scope of the transaction ... always a good idea ... or provide another exit mechanism which won't cause and undo. Note that it is a strong design principle that one should never have a...

Note that the .lic file is connections, which may or may not correspond to users in your license. If you have a concurrent user license, then the big question is whether your users create multiple simultaneous sessions from the same device. If they create 3 sessions, that is 3 connections in...

Have you done a COMPILE LISTING yet on on the programs in the stack?

If I remember correctly, 8859-1 has no euro symbol, but 8859-15 does.

find first is almost always wrong. If the keys provided identity a unique record, then you are sending a false signal to anyone who has to maintain the code since it appears that you want the first of a group. If the keys are not unique, then the implication is that you are treating the first...

There is always a transaction scope, whether you define it explicitly or not. It can propagate down from a higher level program, so a program that looks like it has no scope may still be within a transaction scope. One of the really big reasons to explicitly define scope is so that you can be...

You need to complete the transaction before hitting F4 or you will undo the transaction. Use COMPILE LISTING to see transaction scope.

A great many ABL programmers learn by a combination of looking at code and mentoring from others in the company, supplemented by interactions on forums like this. The tricky part, of course, is whether the code base you are looking at is a good example or a bad example. The latter are more...

There isn't really a good alternative to cleaning up shared variables other than to analyze where they are set and used and to substitute, wherever possible, direct parameter passing. If you do truly have global values that are widely used, it is possible to define an object with static...

Documentation of the columns is in the manual ... remembering, of course, that the .lic file monitors *connections* which are only loosely related to *users* for licensing purposes.

Interesting to speculate on what a developer only version is doing used for production. If you have even one developer license, you should be able to do anything you want to the database ... although, if you don't know what you are doing, you could easily break a lot of things, so deleting...

2002!