Jump to content


tclulow

Member Since 10 Jun 2003
Offline Last Active Aug 16 2011 09:50 AM
-----

Posts I've Made

In Topic: Aggregate Function

13 October 2006 - 04:18 PM

We've had problems using INTO for numeric variables - they get truncated to integers.

Even this:
SQL
select numeric_column into :#VALUE where another_column = :#ANOTHER_VALUE
ENDSQL

Results in #VALUE and #ANOTHER_VALUE being truncated to integer.


I've a feeling that INTO isn't officially supported.


Tony.

In Topic: People using VIP....

24 August 2006 - 04:08 PM

As ProIV are dropping support for native development, maybe you will have to do something in respect of VIP.

As soon as I have a function (from IDE into native) that exhibits a ProIV bug, they'll ask for an example function.
Obviously I can import into VIP and send that (though that's not quite the same). However, once it's in VIP it only takes a moment to gen from VIP and trash the native representation. I haven't found a way in VIP (and don't wish to waste the time finding a way in VIP) to delete the VIP representation and revert to native.

I also haven't found a way to re-import a function from native to VIP after it's been modified in native (whether via IDE or not).

I guess I'm saying I'm not comfortable with two different repositories for the source which aren't synchronised in any way.

Maybe a VIP interface (that I can turn on and off obviously) and the ability to trash the VIP versions in favour of native (which I'm assuming will be quicker).

Tony.

In Topic: display current field name

24 August 2006 - 03:51 PM

Or
@XFUNCT contains the function name to be executed in the event of the user pressing ALT F4 or clicking the X box at the top right.
Apparently

@CPSEQ contains the value of the last sequence number where the cursor was (so I'm told)

@XOFSET (note the spelling)
This variable can be set in Before Field to set the value of the current position in the current field being edited. Useful if there is a long string that the user wishes to edit at a particular place.

@OFFSET (that spelling is less confusing)
Immediately after processing the field this will contain the positional value of where the cursor was within the field when return was pressed.

The last two are (apparently) not detailed in the manual (but I haven't checked - been busy).

Hope these are useful

@XOFSET (note the spelling)
This variable can be set in Before Field to set the value of the current position in the current field being edited. Useful if there is a long string that the user wishes to edit at a particular place.

@OFFSET (that spelling is less confusing)
Immediately after processing the field this will contain the positional value of where the cursor was within the field when return was pressed.

The last two are (apparently) not detailed in the manual (but I haven't checked - been busy).


Last time I tried, @OFFSET didn't work and when I complained, they replied that it was never documented and they could therefore arbirarily remove the functionality - it had worked in earlier versions.

I seem to remember the excuse was to do with proportional fonts being difficult (they claimed not possible).

Tony

In Topic: Another one bites the dust?

03 July 2006 - 04:57 PM

I should further add that in the case I was previously involved with, the Directors tried to pull a trick like this (which is perfectly legal as far as I can tell).

1) Run up big debts.
2) Liquidate the company.
3) Set up a new company and buy the IPR of valuable software from the Liquidator cheaply.
4) Arrange new contracts with the customers of the liquidated company.
5) Return to step 1.

If this turns out to be the case here, then:

To put a spanner in the works, ensure that step 3 doesn't run smoothly. Make sure the Liquidator is aware of the value of the IPR. In our case we bid for the IPR to push the price up The customers may be able to help here. You can also disrupt step 4, make sure they're aware what is going on. This strategy is really designed to work with the customers and employees at the expense of the creditors.

We were also helped by the fact that for historical reasons the bank had a charge on the Director's assets (rather than on the company) so was able to extract its money from the Directors. A certain satisfaction was gained.



Tony.

In Topic: Another one bites the dust?

03 July 2006 - 04:41 PM

unpaid priority wages
secured creditors
general creditors
unpaid wages
stockholders

From my experience of a liquidation, "unpaid priority wages" doesn't exist in UK.

First will be secured creditors (banks usually)
Next the tax man (VAT & IR)
Next the general creditiors (including unpaid wages)
Last Stock holders.

The Government will pay statuatory redundancy to employees if the company isn't able to. In the case that the liquidation takes a long time, the Government pays the employees and takes over that share of the employees rights against the company. Don't expect statuatory redundancy to be very big, it will be very small.

Tony.