APT 5.2.2 to APT 5.3 Problems

[Nic Maclean]

I have come across two problem when converting from a year 2000 non
compliant version of APT to a compliant version.

The versions are APT 5.2.2 to APT 5.3 ( Sybase on AIX )

Does anyone know of :
A. any quick fixes to our problems mentioned below
B. Anything else we may need to be aware of before our new system is
released.

1. Empty string field and null no longer being equal
------------------------------------------------------------------
- we define a field on a form as char length 1

- in APT 5.3 when we perform our check with fpl code against empty string
('') it evaluates as FALSE.

- in our previous version of APT 5.2.2. it evaluates as TRUE ( which is what
we expect to still happen )

- we can work around this by changing the check to 'is null' but this
requires quite a lot of work to be performed as it is not an isolated case !
( We have 10,000+ source fpl files ).

The inconsistency only applies to tests on fields not variables.

example :

test_field = ''

if test_field = ''
begin

...

end

2. <fieldname>.tabable = false fails when cursor on <fieldname>
----------------------------------------------------------------------------
-----------
This problem is to do with cursor positioning and tabable fields.
Basically, in the old version of APT, you could make a field not tabable
when the cursor is currently in this field.
The new version does not allow this.
The field:tabable = FALSE, actually fails and its value remains as TRUE.
Although this does not sound major, it will affect the way our application
works.

For example :
// Note, cursor is on field
field:tabable = FALSE
if field:tabable = FALSE
begin
Used to do this code
end
else
begin
Now does this code as the field will still be tabable !
end
This problem is more significant as we can not search for instances when
this happens.

Please e-mail : Nicola_...@camcable.co.uk
Thanks !