News - Xailer - For users Clipper, VO, VFP, Harbour

[Hurricane]

News, download Xailer, Harbour and Mingw:
English: http://xailer.info/wordpress/en/?p=367
Spanish: https://xailer.info/wordpress/es/?p=1367

Existing for more than 14 years, Xailer is a professional and complete tool for developing applications with Harbour:
Integrated: Form Designer, Project Manager (to create EXE, LIB, DLL), Debugger, DBF and SQLite Editors, Resource Manager, Code Editor (+Intellisense).
Native Access to SQLite, MariaDB/MySQL, ADO, ODBC. DataSource, DataSets, Data controls to: Web, DBF, ADS/ADT, SQLite, MariaDB/MySQL, ADO, ODBC, tables in memory.
Report generator, components for the FastReport product (FRX for [x]Harbour). Creating plugins for IDE.

Xailer executables are completely self-conteined, ie, you do not need any external library or execution environment like .NET or Java, for its execution.

more information: https://www.xailer.com/?start

Gallery of applications written in Xailer:
http://apps.codigoxailer.com/

Free accounting software for download:
https://www.ozs.es/wp/xaconta-local/

regards,
Hurricane

[Mr. Man-wai Chang]

Post by Hurricane
English: http://xailer.info/wordpress/en/?p=367
Spanish: https://xailer.info/wordpress/es/?p=1367
Existing for more than 14 years, Xailer is a professional and complete tool for developing applications with Harbour: ....

Now that with virtualization and Cloud hosting, maybe no Clipper
applications need to be ported to other languages or platforms. :)

[Mr. Man-wai Chang]

Post by Mr. Man-wai Chang

Post by Hurricane
English: http://xailer.info/wordpress/en/?p=367
Spanish: https://xailer.info/wordpress/es/?p=1367
Existing for more than 14 years, Xailer is a professional and complete tool for developing applications with Harbour: ....

Now that with virtualization and Cloud hosting, maybe no Clipper
applications need to be ported to other languages or platforms. :)

Forgot a problem: Year 2038 date problem. Old Clipper applications are
16-bit? Or it is 32-bit?

[dlzc]

Dear Mr. Man-wai Chang:

On Sunday, March 24, 2019 at 8:49:16 AM UTC-7, Mr. Man-wai Chang wrote:
...

Post by Mr. Man-wai Chang
Forgot a problem: Year 2038 date problem. Old
Clipper applications are 16-bit? Or it is 32-bit?

They use Windoze / DOS date format. Clipper's problem was Y2K, not old Linux date format.

David A. Smith

[Mr. Man-wai Chang]

Post by dlzc
...

Post by Mr. Man-wai Chang
Forgot a problem: Year 2038 date problem. Old
Clipper applications are 16-bit? Or it is 32-bit?

They use Windoze / DOS date format. Clipper's problem was Y2K, not old Linux date format.
David A. Smith

But Clipper for DOS is still 16-bit at best. Could a 16-bit integer
handle dates beyond year 2038? You need a 64-bit date....

Disclaim: I am not so sure about Clipper's data structures. I am also
not sure about the Command Prompt of Windows.

[dlzc]

Dear Mr. Man-wai Chang:

On Monday, March 25, 2019 at 6:48:52 AM UTC-7, Mr. Man-wai Chang wrote:
...

Post by Mr. Man-wai Chang
But Clipper for DOS is still 16-bit at best. Could a
16-bit integer handle dates beyond year 2038? You
need a 64-bit date....

Clipper does integer math for year, day, month, hour, minute, second, stored as strings. The STORED date is truncated two two digits of year "assuming" what ever "century" is set for. So dates stored "last century" will have to lots of "guard code" to make them pertinent. Dates are very much controlled by the Windoze machines they run on, and Windoze was fixed before Y2K.

You are thinking of "older Linux".

Post by Mr. Man-wai Chang
Disclaim: I am not so sure about Clipper's data
structures. I am also not sure about the Command
Prompt of Windows.

If it matters to you:
https://www.clicketyclick.dk/databases/xbase/format/dbf.html#DBF_STRUCT
... pointed at by the US LIbrary of Congress website (with an additional selection).
https://www.loc.gov/preservation/digital/formats/fdd/fdd000325.shtml

Clipper, depending on RDD, is downward compatible with dBase III file formats.

David A. Smith

[Klas Engwall]

Hi David,

Post by dlzc
Clipper does integer math for year, day, month, hour, minute, second,
stored as strings. The STORED date is truncated two two digits of year
"assuming" what ever "century" is set for. So dates stored "last century"
will have to lots of "guard code" to make them pertinent. Dates are very
much controlled by the Windoze machines they run on, and Windoze was fixed
before Y2K.

The lupdate() field in the DBF header is truncated to YYMMDD, but a date
field in a DBF record is always YYYYMMDD (D,8,0). However, if you use a
two digit year in the picture format for a date, then Clipper will make
assumptions about what you are typing based on the SET EPOCH setting. So
to avoid problems with dates in "last century", using a four digit year
in the picture format is a good idea.

Regards,
Klas

--- news://freenews.netfront.net/ - complaints: ***@netfront.net ---

[dlzc]

Post by Klas Engwall
Hi David,

Post by dlzc
Clipper does integer math for year, day, month,
hour, minute, second, stored as strings. The
STORED date is truncated two two digits of year
"assuming" what ever "century" is set for. So
dates stored "last century" will have to lots
of "guard code" to make them pertinent. Dates
are very much controlled by the Windoze machines
they run on, and Windoze was fixed before Y2K.

The lupdate() field in the DBF header is truncated
to YYMMDD, but a date field in a DBF record is
always YYYYMMDD (D,8,0). However, if you use a
two digit year in the picture format for a date,
then Clipper will make assumptions about what you
are typing based on the SET EPOCH setting. So to
avoid problems with dates in "last century",
using a four digit year in the picture format is
a good idea.

Thanks for the correction.

David A. Smith

[Johan Nel]

You can rectify that by a mere:

SET EPOCH Year(Date()) - 50, when clipper reads the  YY/MM/DD it will
automatically make lupdate() a rolling century.

But seeing we asking questions about how to support Clipper in a new
environment.  Have you considered X#?

http://xsharp.info

Post by Klas Engwall
Hi David,

Post by dlzc
Clipper does integer math for year, day, month, hour, minute, second,
stored as strings.  The STORED date is truncated two two digits of year
"assuming" what ever "century" is set for.  So dates stored "last
century"
will have to lots of "guard code" to make them pertinent.  Dates are
very
much controlled by the Windoze machines they run on, and Windoze was fixed
before Y2K.

The lupdate() field in the DBF header is truncated to YYMMDD, but a
date field in a DBF record is always YYYYMMDD (D,8,0). However, if you
use a two digit year in the picture format for a date, then Clipper
will make assumptions about what you are typing based on the SET EPOCH
setting. So to avoid problems with dates in "last century", using a
four digit year in the picture format is a good idea.
Regards,
Klas

[dlzc]

Dear Johan Nel:

On Monday, March 25, 2019 at 4:57:21 PM UTC-7, Johan Nel wrote:
...

Post by Johan Nel
But seeing we asking questions about how to
support Clipper in a new environment.  Have you
considered X#?
http://xsharp.info

I am waiting until you finish the "on ramp" for (x)Harbour.

David A. Smith

[Johan Nel]

Good day David,

It will be ready soon... Austin Summit is done, everybody will be back
in the saddle later this week...

Johan

Post by dlzc
....

Post by Johan Nel
But seeing we asking questions about how to
support Clipper in a new environment.  Have you
considered X#?
http://xsharp.info

I am waiting until you finish the "on ramp" for (x)Harbour.
David A. Smith