two problems with the latest version of xHarbour and SQLRDD

Hello,

I've two problems with the latest version of xHarbour and SQLRDD.

First, SET AUTOPEN OFF is not recognize anymore at compile time

The second problem occurs on the sample connect.prg. It seems that
there is an error in HB_ReadIni() because cDatabase IN hIniFile
returns false although cDatabase correspond to a section in
sqlrdd.ini.

Is there something new to do with this version ?

Regards,

mathmax

Hi all

I have posted this to xharbour beta.sqlrdd to no avail ... as no one
responded, I post here to see if I have better luck.

Here it is:
--
In my attempt to migrate to a sql environment, I noted that from 2 ws I can
see the same record and change them as I wish but without contention.
It seems that sqlrdd doesn't lock the record when "dbrlock(recno())" is
executed, in a way that any other workstation have access to the same record
and change it.

My working environment is xharbour nov/2007 (professional version), sqlrdd
demo (included in the package), mysql 5, xp sp2.

I'm using a modified tbrowse, where as soon as I press the <enter> key the
program executes an ad-hoc rec_lock function (which in turn calls dbrlock).
This reclock function test if succesfully locked the record, then presents a
lot of @ say / get on screen so the user can change the info.
If not successfull, I display a message in screen telling that someone else
has this record locked (which will try again or cancels) and do not present
the info (@ say & gets) on screen...

The thing is: the message 'record locked' never appears. It is always
available for "editing".

The very same code works fine under xharbour + rmdbfcdx (32 bits) and/or
clipper + comix (16 bits) or clipper + six3 (16 bits).

Is it a normal behaviour or is there something wrong in this library, a
workaround or something that I don't know about...?
Maybe a configuration option in the mysql server ?

Regards,
--
Lic. Claudio Voskian
ICQ#: 18122595 - Aol/Msn/Skype/Y!: cvoskian
Buenos Aires - Argentina

---
PS: if the 'silence' from the support team is a 'well behaved habit' that
we, as registered users, obtain from the people in charge at xharbour.com,
it's easy to understand the 'no documentation at all' in some parts and
other similar faults from them (no answers at all when something discovered
is not covered in any way), and considering the poor progress in the
development step.
I'm seriously thinking in a move to a different platform; xharbour or
clipper is not the only one in the horizon.

(Think of it as a clever warning, if you wish; or move this to the thrash
bin).

Claudio,

Your question was responded in Beta Newsgroup in sep 02, 10:21 am.
Please let me know if I can help you further.

Best Regards,

Marcelo

On Aug 31, 7:23*pm, "Claudio Voskian" <mixxell-nosp...@hotmail.com>
wrote:
> Hi all
>
> I have posted this to xharbour beta.sqlrdd to no avail ... as no one
> responded, I post here to see if I have better luck.
>
> Here it is:
> --
> In my attempt to migrate to a sql environment, I noted that from 2 ws I can
> see the same record and change them as I wish but without contention.
> It seems that sqlrdd doesn't lock the record when "dbrlock(recno())" is
> executed, in a way that any other workstation have access to the same record
> and change it.
>
> My working environment is xharbour nov/2007 (professional version), sqlrdd
> demo (included in the package), mysql 5, xp sp2.
>
> I'm using a modified tbrowse, where as soon as I press the <enter> key the
> program executes an ad-hoc rec_lock function (which in turn calls dbrlock).
> This reclock function test if succesfully locked the record, then presents a
> lot of @ say / get on screen so the user can change the info.
> If not successfull, I display a message in screen telling that someone else
> has this record locked (which will try again or cancels) and do not present
> the info (@ say & gets) on screen...
>
> The thing is: the message 'record locked' never appears. It is always
> available for "editing".
>
> The very same code works fine under xharbour + rmdbfcdx (32 bits) and/or
> clipper + comix (16 bits) or clipper + six3 (16 bits).
>
> Is it a normal behaviour or is there something wrong in this library, a
> workaround or something that I don't know about...?
> Maybe a configuration option in the mysql server ?
>
> Regards,
> --
> Lic. Claudio Voskian
> ICQ#: 18122595 - Aol/Msn/Skype/Y!: cvoskian
> Buenos Aires - Argentina
>
> ---
> PS: if the 'silence' from the support team is a 'well behaved habit' that
> we, as registered users, obtain from the people in charge at xharbour.com,
> it's easy to understand the 'no documentation at all' in some parts and
> other similar faults from them (no answers at all when something discovered
> is not covered in any way), and considering the poor progress in the
> development step.
> I'm seriously thinking in a move to a different platform; xharbour or
> clipper is not the only one in the horizon.
>
> (Think of it as a clever warning, if you wish; or move this to the thrash
> bin).

Marcelo

Thank you for your response, I've seen your answer in the beta.sqlrdd
newsgroup, but didn't get the time to isolate the fault in a small example
yet (in fact, no time to do anything with xharbour).
Will try next days.

CU,
--
Lic. Claudio Voskian
ICQ#: 18122595 - Aol/Msn/Skype/Y!: cvoskian
Buenos Aires - Argentina


"Marcelo Lombardo" <marcelo@xharbour.com.br> escribió en el mensaje
news:4a45b820-c77d-46f7-8d87-53ef8f0c2486@73g2000hsx.googlegroups.com...
Claudio,

Your question was responded in Beta Newsgroup in sep 02, 10:21 am.
Please let me know if I can help you further.

Best Regards,

Marcelo

On Aug 31, 7:23 pm, "Claudio Voskian" <mixxell-nosp...@hotmail.com>
wrote:
> Hi all
>
> I have posted this to xharbour beta.sqlrdd to no avail ... as no one
> responded, I post here to see if I have better luck.
>
> Here it is:
> --
> In my attempt to migrate to a sql environment, I noted that from 2 ws I
> can
> see the same record and change them as I wish but without contention.
> It seems that sqlrdd doesn't lock the record when "dbrlock(recno())" is
> executed, in a way that any other workstation have access to the same
> record
> and change it.
>
> My working environment is xharbour nov/2007 (professional version), sqlrdd
> demo (included in the package), mysql 5, xp sp2.
>
> I'm using a modified tbrowse, where as soon as I press the <enter> key the
> program executes an ad-hoc rec_lock function (which in turn calls
> dbrlock).
> This reclock function test if succesfully locked the record, then presents
> a
> lot of @ say / get on screen so the user can change the info.
> If not successfull, I display a message in screen telling that someone
> else
> has this record locked (which will try again or cancels) and do not
> present
> the info (@ say & gets) on screen...
>
> The thing is: the message 'record locked' never appears. It is always
> available for "editing".
>
> The very same code works fine under xharbour + rmdbfcdx (32 bits) and/or
> clipper + comix (16 bits) or clipper + six3 (16 bits).
>
> Is it a normal behaviour or is there something wrong in this library, a
> workaround or something that I don't know about...?
> Maybe a configuration option in the mysql server ?
>
> Regards,
> --
> Lic. Claudio Voskian
> ICQ#: 18122595 - Aol/Msn/Skype/Y!: cvoskian
> Buenos Aires - Argentina
>
> ---
> PS: if the 'silence' from the support team is a 'well behaved habit' that
> we, as registered users, obtain from the people in charge at xharbour.com,
> it's easy to understand the 'no documentation at all' in some parts and
> other similar faults from them (no answers at all when something
> discovered
> is not covered in any way), and considering the poor progress in the
> development step.
> I'm seriously thinking in a move to a different platform; xharbour or
> clipper is not the only one in the horizon.
>
> (Think of it as a clever warning, if you wish; or move this to the thrash
> bin).

Hello Claudio,

> Thank you for your response, I've seen your answer in the beta.sqlrdd
> newsgroup, but didn't get the time to isolate the fault in a small example
> yet (in fact, no time to do anything with xharbour).
> Will try next days.

Reading this, I'm a disappointed in your previous answer Claudio. You
said: "I have posted this to xharbour beta.sqlrdd to no avail ... as no
one responded, I post here to see if I have better luck."

This makes people think we don't offer tech support on our products.

--

Sincerely,

Patrick Mast,
xHarbour.com

Patrick

At least, you have read all my post and that is good news.
I don't want to apologyze with you; I'm not offending anyone expressing my
feelings.
It would be an infinite discussion, but that's it.

I'm a registered user using xh professional.

It's a fact that the answer you or someone else from your company (Marcelo,
Luiz, Ron, etc.) are giving to the users is not what we deserve. I'm not
telling you/they are bad professionals, no, they are very very good, all of
you.
A different thing is the way the support is given.

There were a lot of questions that I or other people have posted here or in
other newsgroups hosted by xharbour.com, that were NEVER answered, and this
is a fact.

So, if you don't think that something could be done to change this defacto
behaviour from your side (as your company sells this product and try to earn
money with people like me or a big corporation), I or anyone will look to
another place or flavour to develop applications.
As I said xh is not the only choice; just a bit of interest from your side
may do a big difference in my (our) perception of the reality.

To start with:
- the 30 days of free support after purchase (which should be, at least, 90
days or even more), to the fact that I purchased a version that was really
buggy, and after the first 30 days and not being published a new and
corrected version I have had to circumvent the Bugs included with code that
should be/is freely available, but only if the user knows what and where to
look for, that is not my case. I'm not an expert in C, compilers or such
complex things - I just go and do businness. My feeling is that such
corrections should be freely available because I paid for something NEW that
came broken in the box.
- answering questions emphatically in the newsgroups; of course, you need
time and the answers should be as fast as you can (not a week or more, or
never answer; I posted a couple of threads to which nobody paid attention
to).
- publishing the needed documentation for all the libraries, functions,
procedures, classes, methods, etc. etc. (you posted something days ago). If
it came in a printed book, much better.
- publishing patches for your registered users; they are/were customers
after all.

As you can see, there are different points of view of the same thing.
I'm a user who provide customers with applications that fills their needs.
If I made a mistake, it's my fault and I do everything I can to solve it and
have my customers happy. They can change their mind and think: "Hey, Claudio
is making such kind of mistakes, let's find a better solution with someone
else" and then I lost a client and money.

Finally, I don't do any objections to the price of your products. "It's the
market, stupid" said someone a little clever than me.

That said, I finished this thread expecting that my opinions don't hurt
anybody but do reflect my point of view.

Have a nice day.
--
Lic. Claudio Voskian
ICQ#: 18122595 - Aol/Msn/Skype/Y!: cvoskian
Buenos Aires - Argentina

"Patrick Mast" <Patrick.RemoveThis.Mast@xHarbour.com> escribió en el mensaje
news:2008090408490416807-PatrickRemoveThisMast@xHarbourcom...
> Hello Claudio,
>
>> Thank you for your response, I've seen your answer in the beta.sqlrdd
>> newsgroup, but didn't get the time to isolate the fault in a small
>> example
>> yet (in fact, no time to do anything with xharbour).
>> Will try next days.
>
> Reading this, I'm a disappointed in your previous answer Claudio. You
> said: "I have posted this to xharbour beta.sqlrdd to no avail ... as no
> one responded, I post here to see if I have better luck."
>
> This makes people think we don't offer tech support on our products.
>
> --
>
> Sincerely,
>
> Patrick Mast,
> xHarbour.com
>

Hey Claudio,

Thank you for your thoughts. We will surely take your concerns in account.
--
Sincerely,

Patrick Mast,
http://www.xHarbour.com