Jump to content

Andy Jones

Member Since 12 Mar 2003
Offline Last Active Sep 17 2003 12:52 AM

Posts I've Made

In Topic: Width in Report function

24 July 2003 - 05:45 PM

Hi Dominik,

Do you mean that the report isn't working correctly, or that you can't define text in the format past 132 columns?

If you can't enter text past that column, then try altering the value variable &#@REPCOL, setting it to your desired maximum width. (&#@REPROW is maximum lines per page)

I think only @MOD/@MODX enforce those values.



In Topic: 4.6 to 5.5 Upgrade

24 July 2003 - 05:31 PM

yeah you are Rob :p

There is no reason to go via 5.0 as 5.5 was an evolution of 5.0. (addition of ActiveX etc)

The upgrades required between 4.6 and 5.x code are done automatically by Import, so just import into 5.5.
Bringing old code into 5.x also requires a mandatory Re-Gen of all functions - so DO NOT just copy/ISIN your application bootstraps to a 5.5 area or try to run 4.6 bootstraps with a 5.x kernel. It will try to regen LOGON - and then you won't be able to log in!

If you do somehow manage to bring old function source into a 5.x area without using the proper Import routines, then you'll need to run the two tools in the 'Additional Utilities' menu @UM2 - Convert Radio Buttons and GUI Attributes Conversion - to fix up your functions. As I say these utils are only required if you didn't bring your code in via Import.

One potential problem area can be very large screen functions breaking function size limits under 5.x.
This is due to the addition of object tags and properties which increases the function size - I believe this has been covered in other topics on this site.


16 July 2003 - 12:05 PM


FYI - the behaviour of the Primary Input field and forcewrite were covered in detail in this thread:

Have you tried returning your data to $INPUT rather than the field's variable?
Doing this this will force the cursor to the next field on returning from the window, so the data should then be written away if the user arrows/F3's.




09 July 2003 - 05:16 PM

If you don't mind the DOS box flashing, you could use:


Using START will run most windows applications without your PROIV app needing to know what path they are installed under...

START on NT/2000/XP is a command shell verb (run with /? for its switches) but if I recall correctly it is an executable on windows 9x, so if you know for a fact all your clients are running on 9x you could probably use the WINDOWS verb to suppress the dos box.
Using START you can MINimise or MAXimise the launched application too. :(

If you want to open a specific web page, just tack it onto the end of your command -

oh, a small word of warning when using explicit path names...
the ~1 component of shortened directory names is not always a certainty, it all depends what was on the drive when windows was installed, and if there are other folders with the same first 7 chars.... I've seen Progra~2 before now...




08 July 2003 - 11:02 PM

I cannot get :
#X = SYSTEM('GUI WINDOWS dir >dir.txt')
to run and create a file on the drive. It "runs" and returns and the function carries on, but no joy on the data file :) .

I get a stop button with the message "Unable to execute local command" message.

The reason your DIR command doesn't work is because you've used the WINDOWS keyword. It's only of use when you are intending to run an executable file (program or batch file).
In your example DIR is a shell command.

To execute shell commands such as DIR, just drop the 'WINDOWS' part.
i.e. #X = SYSTEM('GUI dir >dir.txt')

That should work!