🚀 go-pugleaf

Is Visual dBase dead?
Version 7.01 - disappointing, faulty, sluggish, complicated.
Scorn of Inprise (and now, Interbase, and tomorrow, the trash). In this
version, a simple task of to do with VDB 5.5, becomes tedious and very
dificult.
Why to use an 'one-legged SQL'?  The lackof date's function is an delay of
life, since the most of commercial applications needs it.   For example, the
QBE file bellow, fast and simple, is the base for a report what presents all
liabilities for to pay up to the present, inclusively conquereds.

INCLUIR .QBE
* dBASE Windows arquivo .QBE 9
CLOSE DATABASES
SET EXACT ON
SET DELETED ON
SELECT 1
USE C:\VISUALDB\CAIXA\CONTAPAG.DBF ORDER TAG NOME
SET FILTER TO VENC<=DATE() .AND. EMPTY(PGTO)  // (this line, the Vdb7 dmd
fails, sql fails, it's the bad complication of Vdb7. Filters and params,
many complications, insufficient performance)
SET FIELDS TO COD,NF, DV, NN, VALOR, VENC, VERIF, NOME, REL, PGTO, BANCO
GO TOP

Well, in Vdb7 the complication is great.  For to do the same task, we need
not a qbe and rpt files, but many other files (dmd, sql, wfm, rep), what
don't work. The manual is very bad. And the worst is the desinterestedness
of Borland/Inprise/Interbase.  This company needs only an autopsy. Inprise,
to change the name for to hide your execrable reputation don't resolve!  Or,
change the name to Delphi, your unique interest, but this, with four
versions and many, many patches in only three years... it's very unstable,
too.  In our applications, we shall continue to use Visual dBase 5.5 / 5.6,
during some time, because the 'RAD' (???!!!) VDB7 don't exists, or is dead.
Any help is welcome.  Jarbas