Hello,
In previous builds, issuing xBrowse(oObject), when the object was empty showed an empty xbrowse(), but now it shows the current dbf.
It should show an empty xbrowse or a message saying that oObject is empty.
Thank you.
Moises,
That behavior has not changed since 2013 or even earlier.
To me it is not wrong, as it is using the default Alias().
Why don't you close the DBF before calling Xbrowse( oObject ) ?
Antonio,
Several times, I use xBrowse( oObject ) to do debugging, not for browsing the table.
For browsing the table, I do xbrowse() or xbrowse( alias() ).
In the past, when oObject was empty or nill, xBrowse showed empty. That was great.
Now, when the Object passed in the function is not empty, it browses it. Otherwise, this is the problem, now browses the dbf, not an empty object as in the past.
I am sure there is a bug. Maybe Mr. Nages could confirm it?.
Thank you.
function XBrowse( uData, cTitle, lAutoSort, bSetUp, aCols, bSelect, lExcel, lFastEdit, ;
bValid, cSerial )
...
DEFAULT uData := Alias()function main()
 local myvar := {}
 use testing
 xbrowse( myvar )
return nilfunction main()
 local myvar
 use testing
 xbrowse( myvar )
return nilMr Antonio is correct. When uData is nil, xbrowse displays default Alias(). This has been the behavior since the time this function was created and this behavior is intentional.
We intended that simple statement
XBrowse() or
XBROWSER
shows the default alias, same way the function Browse() does. ( Browse() uses WBrowse )
When there is no DBF open yet then this function shows an empty browse.
You can use (0)->( XBrowse( MyVar ) ) to get what you want.
Thank you for your clarifications.
I guess in the past I modified in the lib xbrowse() removing default cAlias := alias().
For my purpouses, I created a personal UDF.
