DBSELECTAREA( 0 ) bug

[Antonio Linares]

Due to recent Harbour changes, this code that used to work this way:

USE CUSTOMER
? SELECT() // --> 1
DBSELECTAREA( 0 )
? SELECT() // --> used to return 2, now it is returning ZERO !!!

Has clearly changed its behavior affecting many Harbour apps.

It seems as DbSelectArea( 0 ) has changed its behavior. 

Reported by several Harbour users and confirmed by us.

many thanks

[Enrico Maria Giordano]

Il 06/03/2024 22:55, Itamar M. Lins Jr. Lins ha scritto:

> Hi!
> For me it was wrong.
> Now it's right
> DbSelectArea(0) should return zero, and not 2, where did this 2 come from?
> If it's the clipper's behavior, I don't even know if it's worth leaving
> this BUG. If you are being asked to select area zero and it returns two,
> it is a BUG.
> And if it's area 3,4,5...
> Will return 2?
> I've never used this, is it wrong for me, ghost area? News.

Work area 0 has a special meaning: it selects the next unused work area.

--
Enrico Maria Giordano

http://www.emagsoftware.it
http://www.emagsoftware.it/emgmusic
http://www.emagsoftware.it/spectrum
http://www.emagsoftware.it/tbosg

[Itamar M. Lins Jr. Lins]

Hi!

Yes my fault. This is a old feature of dbSelectArea()

Best regards,
Itamar M. Lins Jr.

--
You received this message because you are subscribed to the Google Groups "Harbour Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to harbour-deve...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/harbour-devel/78109767-84c3-4b81-a7ee-08121392db75%40emagsoftware.it.