Xbase and ADT tables NULL value
Posted: Fri Nov 04, 2011 9:54 am
Hi,
We were planning to convert our tables to Advantage ADT files. We thought we could convert and use the same source with some minor modifications, it's compatible with ADSDBE, and to move to a complete SQL syntax at the end.
Compatible seems to be something different in Belgium.
The following is working:
customer->(dbappend())
customer->number := 123
customer->name := cName
....
So good so far, but now the problem starts for each field which isn't replaced after the append.
Suppose there is a numeric field customer->totalsale, this remains a NULL field. So if you afterwards have a report where you want to print customer->totalsale you can't! You have to check if this field is a numeric or NULL field.
Suppose there is a character field customer->remark which isn't replaced with space(xx) after the append, it remains a NULL field. If you have valtype(customer->remark) it won't give Character afterwards.
In our software we have hundreds of fields which aren't filled at the moment of the record creation. They are filled when there is data for it. With these NULL fields, our ADT table doesn't give the same result as DBF tables.
Anyone who have tried this? Is this a problem with SQL-Express?
I know you can define 'default value' in your table, but this should be done for every field? And what happens if a new field is added to an existing table. The existing records have a NUL value, only new records are getting the default value.
Also the ACE function to convert a DBF to ADT file is creating the ADT table with NULL fields for all the empty character fields. Strange enough, it doesn't create NULL fields for numeric fields. On the other hand, if you append(), a numeric is a NULL field.
We were planning to convert our tables to Advantage ADT files. We thought we could convert and use the same source with some minor modifications, it's compatible with ADSDBE, and to move to a complete SQL syntax at the end.
Compatible seems to be something different in Belgium.
The following is working:
customer->(dbappend())
customer->number := 123
customer->name := cName
....
So good so far, but now the problem starts for each field which isn't replaced after the append.
Suppose there is a numeric field customer->totalsale, this remains a NULL field. So if you afterwards have a report where you want to print customer->totalsale you can't! You have to check if this field is a numeric or NULL field.
Suppose there is a character field customer->remark which isn't replaced with space(xx) after the append, it remains a NULL field. If you have valtype(customer->remark) it won't give Character afterwards.
In our software we have hundreds of fields which aren't filled at the moment of the record creation. They are filled when there is data for it. With these NULL fields, our ADT table doesn't give the same result as DBF tables.
Anyone who have tried this? Is this a problem with SQL-Express?
I know you can define 'default value' in your table, but this should be done for every field? And what happens if a new field is added to an existing table. The existing records have a NUL value, only new records are getting the default value.
Also the ACE function to convert a DBF to ADT file is creating the ADT table with NULL fields for all the empty character fields. Strange enough, it doesn't create NULL fields for numeric fields. On the other hand, if you append(), a numeric is a NULL field.