FiveTech Support Forums

I just recompiled my program with FWH 10.3. Date fields are now displaying the date and then a time, ie. 03/30/2010 00:00:00:00

This is causing problems with the column sizing.

Is there a setting or fix ?

FWH 10.3
xHarbour Professional November 2009

The code:
add to oLbxo header "Due Date" data oWrkOrd:duedat ALIGN LEFT SIZE 100

The field is a date field drawn from the database.

This is a new behavior starting with 10.3. Prior to this, xBrowse displayed the date with no problem, so there was apparently a change made on this release.

Rao,

I have never seen this caret syntax.

{^ 2009/10/10}

Does this automatically convert the value to a date format?

James

James Bott wrote:Rao,

I have never seen this caret syntax.

{^ 2009/10/10}

Does this automatically convert the value to a date format?

James

Rao,

Now we can assign date constants to static variables easily.

static tDate := {^ 2000/10/09 15:15:15 }

Hmm, only for statics, not locals?

What does valtype( tDate ) return?

James

Hmm, only for statics, not locals?

Mr. Tim

The xHarbour function HB_isDateTime( <var> ) is expected to return .f. when the date variable does not have timepart and .t. when the variable has timepart also.

Several versions back, XBrowse used HB_IsDateTime() to ascertain whether the variable has time-part or not. But in some versions of xHarbour, there was a bug in this function and HB_isDateTime() was returning .t. for all dates, even without time part. At that time XBrowse had a temporary workaround to check if the variable has time-part or not. Now that the bug is resolved in the recent versions of xHarbour, XBrowse again reverted to the old code ( in version 10.3 ) and is now depending on HB_IsDateTime().

Will you please help by checking what is the result of ? HB_IsDateTime( Date() ) in your version of xHarbour?

This will help reinstating the time-part check.

It may not be out of place to mention a few hints to take the best advantage of XBrowse's built-in capabilities.

If we use the syntax, XBROWSE .... COLUMNS 'col1', 'col2' ... ALIAS <calias> or OBJECT <dataobj>, XBrowse extracts the exact information about the datatype, datalen and datadec from the DbStruct() or oData:aStruct and appropriately decides the correct format, alignment and column width for display. In addition, XBrowse constructs the bOnPostEdit blocks, with shares and locking appropriately/

If we use FIELDS clause or ADD COLUMN syntax, we are preventing XBrowse to learn the information and we naturally take more responsibility to define picture clause, width, bOnPostEdit block, etc.

Using COLUMNS clause not only compacts the code and easier to maintain but also gets a superior performance.

If we use the syntax, XBROWSE .... COLUMNS 'col1', 'col2' ... ALIAS <calias> or OBJECT <dataobj>,

I am adding PICTURE "@D" to my xbrowses that use a date. When I first started coding with xbrowse it did not automatically format the fields correctly, so I did it this way. Eventually I may be able to revise the code but there is too much to do at this time. The PICTURE statement is a quick fix for now.

I'm using Nov 2009 which was the last comprehensive build ... non-beta.

When running your test function, it returns .t.

Tim

TimStone wrote:
When running your test function, it returns .t.
Tim

James Bott wrote:Rao,

If we use the syntax, XBROWSE .... COLUMNS 'col1', 'col2' ... ALIAS <calias> or OBJECT <dataobj>,

Can you explain in more detail about using the OBJECT clause, perhaps by providing an example. I am particularly wondering about how you would specify only some fields--not all fields.

James

#include 'fivewin.ch'
#include 'ord.ch'
#include 'xbrowse.ch'

REQUEST DBFCDX

function Main()

   local oDbf, oDlg, oBrw

   SET DATE ITALIAN
   SET CENTURY ON
   SET TIME FORMAT TO 'HH:MM:SS'

   RDDSetDefault( 'DBFCDX' )
   oDbf  := TDataBase():Open( , 'CUSTOMER' )
   oDbf:SetOrder( 'FIRST' )

   DEFINE DIALOG oDlg SIZE 550,400 PIXEL
   @ 10,10 XBROWSE oBrw SIZE -10,-10 PIXEL OF oDlg ;
      COLUMNS 'First', 'Married', 'HireDate', 'Salary', 'Age' ;
      OBJECT oDbf ;
      AUTOSORT CELL LINES NOBORDER

   oBrw:Married:SetCheck()
   oBrw:nStretchCol  := 1
   oBrw:CreateFromCode()

   ACTIVATE DIALOG oDlg CENTERED
   oDbf:Close()

return nil