Elvira,
> Glad to see here. It is always a pleasure to talk with one of the xHarbour
> fondunders.
> Hope also you keep participating and helping Andy to support the compiler,
> once Viktor
> and others left xHarbour forever.
Thx, but Victor had never left xHarbour, as he never was involved with
xHarbour. Not sure whom are you referring to by "others", but I will be
happy to respond to specifics.
> First, my framework is xHarbour, latest Fivewin, BCC 5.82 and MySQL 5.x.
> The program has over 20 dfbs with an average of 150 records. Here I start
> with trouble,
> as Luiz and Patrick do not like Fivewin and the pre-definied reply is: “it
> is a Fivewin
>issue, claim Fivetech”.
Please try to avoid speculations, it is not that they don't like FWH, that
is not what they told you. What they did try to explain is that in our
testing we MUST EXCLUDE all 3rd party products. If you CAN NOT REPLICATE a
problem withOUT using some 3rd part product then it is fair to claim that we
can not be THE RESPONSIBLE PARTY.
Let me ask you, what would you do if one of your clients told you that your
program keep failing on machines that have let's say uTorrent, but that it
works perfectly when uTorrent is not on the machine. What would you tell
them when they tell you that NO OTHER PROGRAM has problem with uTorrent only
your program so it must be that your product is defective. When you try to
explain that as they know your product works correctly without uTorrent so
that maybe the problem is with uTorrent, they tell you that you have a
predefined answer that you don't like uTorrent. Even if you did have the
resources and the interest to test with uTorrent what could you really do if
you do not have their source code?
> But it is not. For testing I use the same data content and same program
> of course. With
> DBFCDX or ADSRDD I do not get any issue. Everything is working fine. No
> issues at
> all!!.
Similarly I can claim that SQLRDD works perfectly with xHarbour as you saw
yourself, everything is working fine. No issue at all!!!
> The first issue is that I can´t use xBrowse anymore. With previous SQLRDD
> versions it
> was possible. I think it has to do with Ord…. functions. That worked
> before and now
> does not work anymore. RDDADS works perfect with Ord…. And I can´t remove
> the
> browsing system of our line of software for obvious.
What is the exact Error Message? Have you looked at xBrowse code and tried
to ISOLATE the problem?
If any Ord*() is not working properly it should be very easy to demonstrate
in a reduced sample. Obviously, you don't have to involve FWH in order to
test any of the functionality of a DB product.
> I do experience random GPFS with no error.log or sqlerror.txt. For
> example, I just go to a
> REPORT, starts building it with the Fivewin´s TREPORT system (I get the
> message of
> building page 1), and it crashes. Very hard to trace it. Next week it may
> be working.
> Same test with same data content in DBFCDX or RDDADS works perfect. No
> issues at
> all.In fact, Lucas showed a sample and he was just ignored. xHarbour.com
> refused to
> test with Fivewin.
Elvira, please try to stay focused. SQLRDD is an RDD, it doesn't require any
GUI to TEST its functionality. If something is not working properly, or is
broken then it should be visible withOUT FWH as well!!! All you or Lucas
have to do is the BASIC DUE DILIGENCE of creating a SMALL, REDUCED, SELF
CONTAINED, sample. This is the most efficient way to find bugs anyway, and I
practice it myself everyday that I program.
> As you do not provide any source code, I can´t just trace it. I understand
> the internals
> should kept private. But the rest of the functions and modules should be
> available.
Well this is a completely unrelated issue. Please let's focus on the
TECHNICAL issues.
> Next, from time to time I experience sudden slowness, not related to huge
> tables in
> particular (remember, average is 150 records). Closing the software and
> starting again
> solves it.
If this was an SQLRDD problem then clearly this should be easy to reproduce
in a reduced sample. Please think as a programmer. the RDD doesn't know nor
care what you use for GUI, and if it is SLOW then it must be slow also
withOUT FWH.
> Data is not properly updated. For example, when I have various PCs adding
> a
> customer at almost the same time, they always get the same number:
> DbGoBottom()
> nNUMERO = FIELD->NUMERO+1
Here is a GREAT EXAMPLE of BAD CODE, which demonstrates that you are not yet
aware of some satellites of problems and solutions for Concurrent Usage of
DB, by multiple users. The above code is simply not M/U safe. Instead some
sort of granulated, concurrency protected logic, should be used. You should
not code based on ASSUMPTIONs. Instead you should create code that
EXPLICITLY address the issue at end. For example:
OBTAIN EXCLUSIVE ACCESS to some resource.
OBTAIN VALUE and INCREMENT Numerator.
RELEASE EXCLUSIVE ACCESS
The above pseudo code is the only way to guarantee functionality of
INCREMENTAL NUMERATORs under concurrency demands.
> Also, I detected that SUM command is very slow.
Surely it should be easily demonstrated with a REDUCED, SELF CONTAINED,
sample. Please provide a sample to support your observation.
> I have a table with 100 fields, two records and a total size of 16 kb.
> Browsing, reporting
> it or doing a do while takes too much time. Only two records and almost 65
> seconds.
Surely it should be easily demonstrated with a REDUCED, SELF CONTAINED,
sample. Please provide a sample to support your observation.
> Those kind of errors show that the product is not tested enough. The
> design concept of
> the product hooked me and we decided to choose it. But the truth is that
> the product
> lacks proper testing and debug.
Let me disagree. I believe that your observation are based on intuition and
emotions rather then verifiable technical review. Since the product is in
daily use by many large operations it is fair to assume that your
observations are simply incorrect.
Ron