Search results

Hi, I've used VPE with openedge, without any known issues. Openedge 10.1A I think it was. Greetz

Use the property : suppress-window of the .w, and then use this window on a frame.

Hi Kenny, Maybe you can count the number of 'newlines' in the screen-value of the editor (chr(13)). The n-th line is the line you need...

You can also check the control-load section in the appbuilder generated *.w file. There you have the physical name of the ocx, the *.w is looking for to get started up.

I think you should do this by using a work-file or temp-table...

Take a look at http://en.wikipedia.org/wiki/ISO_7812

Leave out the "CHARACTER" expression in your substring expression. Progress defaults a "CHARACTER" expression to 8 characters. So it returns you a string containing all the needed characters, but displays/put/exports only 8 of them.

If you have to read/write in different files at the same time, you must use the 'stream' equivalent of the I/O operations. So, not output to value("..."). output close. But : output stream s1 to value(" ... "). output stream close. "Input", in the same way. You can use up to 8 streams...

Take a look at : http://www.oehive.org/node/467 there you can find the windows.i (and other) file(s).

So I put you right on track then :-) Enjoy!

Using progress db you have 2 options: The DB is running in single mode or the DB is running in multiuser mode 1. Single user : you have to connect with the -1 option 2. Multi user : you MAY NOT use the -1 option, but, there should be a 'server running' for your database. Starting a...

I'll post a new example. The wrx is just to show something on the startup screen (microsoft treeview). Take a look at this new example: (i'm using OE 10.1a2)

It doesn't have to be that complicated. You have to use the suppress-window property of your "child" window. Look at this example

Take a look at this simple example...

Just as I told you 'ages ago'.... :-))

If the keyfields that you're updating aren't in the where-condition, then you don't have to use the preselect option. Progress doesn't build a result list that matches your query (for each....) first. So it starts the for each... and does continue until there are no more records to find that...

Take a look at the keyword : "PROVERSION"

You're probably updating your keyfields. Use a preselect each to get a result list for your query in memory, before you begin updating your keyfields.

Test the size of ptr with get-size(ptr). Only if it is bigger than 0, try following : message get-string(ptr,1,5) --> get the first 5 bytes of your memptr (only if size allows this, if size is only 4 byte, then get-string(ptr,1,4)... To assure you have something in the ptr.

Can't you do it with running a separate window persistently? And then access procedures and functions in this window using the handle you assigned to it when you ran the window persistent.