Problems with datasets

Dionisis Divaris · Sab Jun 20, 2009 1:11 pm

Hello Ignacio,Jose
I faced with a bad situation due to the last changes on DataSets. I have an
application witch it is a bit before distribution stage and i have the
following serious problems:
To update various application datasets i use the folowing methodology
With Object ::datasetName
:dataSetFieldName:= anyValue
.....
....
:Update()
End With
This is not working when compiled with June version of Xailer. When i
compiled with March version works as
expected. What this happens and how is possible to avoid this 'bad taste'.
I need an answer on this ASAP if it possible due to time frame for
distribution.
TIA
Dionisis

gerencia · Mensaje por **gerencia** » Sab Jun 20, 2009 6:01 pm

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000066">
Hello, Dionisis, 
 
Adds :Edit() 
 
Â Â With Object ::datasetName
 
Â Â Â Â Â Â <big>:Edit() // It is now necessary</big> 
Â Â Â Â Â Â :dataSetFieldName:= anyValue
 
Â Â Â Â Â Â .....
 
Â Â Â Â Â Â ....
 
Â Â Â Â Â :Update()
 
Â Â End With
 
 
 

<div class="moz-signature">
<meta http-equiv="Content-Type" content="text/html; ">
<meta name="ProgId" content="Word.Document">
<meta name="Generator" content="Microsoft Word 12">
<meta name="Originator" content="Microsoft Word 12">
<link rel="File-List" href="Firma%20Audi_archivos/filelist.xml">
<title>José David Angulo</title>
<link rel="themeData" href="Firma%20Audi_archivos/themedata.thmx">
<link rel="colorSchemeMapping"
href="Firma%20Audi_archivos/colorschememapping.xml">

<style>

</style>
<meta name="CREATED" content="20061023;14550935">
<meta name="CHANGEDBY" content="Jose Angulo">
<meta name="CHANGED" content="20061023;14593800">

<div class="Section1">
José David Angulo
Urzola.<o:p></o:p>
Auditoria
y Sistemas Ltda.<o:p></o:p>
<a
href="mailto:Gerencia@microexpressltda.com">jose.angulo@auditoriaysistemas.com</a><o:p></o:p>
Tel.
(57) 5-6643022 â€“ 6644555<o:p></o:p>
Â Cartagena â€“
Colombia<o:p></o:p>
</div>
</div>
 
 
Dionisis Divaris escribió:
<blockquote cite="mid:[email=4a3cc3ca@svctag-j7w3v3j.]4a3cc3ca@svctag-j7w3v3j.[/email]" type="cite">Hello
Ignacio,Jose
 
 
I faced with a bad situation due to the last changes on DataSets. I
have an application witch it is a bit before distribution stage and i
have the followingÂ serious problems:
 
To update various application datasets i use the folowing methodology
 
 
Â Â With Object ::datasetName
 
Â Â Â Â Â Â :dataSetFieldName:= anyValue
 
Â Â Â Â Â Â .....
 
Â Â Â Â Â Â ....
 
Â Â Â Â Â :Update()
 
Â Â End With
 
 
This is not working when compiled with June version of Xailer. When i
compiled with March version works as
 
expected.Â What this happens and how is possible to avoid this 'bad
taste'. I need an answer on this ASAP if it possible due to time frame
for distribution.
 
 
TIA
 
Dionisis
 
 
 
 
</blockquote>
</body>
</html>

Dionisis Divaris · Sab Jun 20, 2009 10:45 pm

José David Angulo Hello Jose
Your code works with March Version but not working with June version . No error occurs when fielde are updating
but no values writen back to the fields of dataset.
TIA
Dionisis
ÎŸ "José David Angulo" <gerencia@microexpressltda.com> ÎÎ³ÏÎ±ÏˆÎµ ÏƒÏ„Î¿ Î¼Î®Î½Ï…Î¼Î± news:[email=4a3d0818@svctag-j7w3v3j....]4a3d0818@svctag-j7w3v3j....[/email]
Hello, Dionisis,
Adds :Edit()
With Object ::datasetName
:Edit() // It is now necessary
:dataSetFieldName:= anyValue
.....
....
:Update()
End With
José David Angulo Urzola.
Auditoria y Sistemas Ltda.
jose.angulo@auditoriaysistemas.com
Tel. (57) 5-6643022 â€“ 6644555
Cartagena â€“ Colombia
Dionisis Divaris escribió:
Hello Ignacio,Jose
I faced with a bad situation due to the last changes on DataSets. I have an application witch it is a bit before distribution stage and i have the following serious problems:
To update various application datasets i use the folowing methodology
With Object ::datasetName
:dataSetFieldName:= anyValue
.....
....
:Update()
End With
This is not working when compiled with June version of Xailer. When i compiled with March version works as
expected. What this happens and how is possible to avoid this 'bad taste'. I need an answer on this ASAP if it possible due to time frame for distribution.
TIA
Dionisis
--

Dionisis Divaris · Dom Jun 21, 2009 12:02 am

José David Angulo To see the problem here is a portion of my coding:
WITH OBJECT TForm13():New(self)
nResult:= :ShowModal()
END WITH
IF nResult == mrCANCEL
::oStorage:FilUnlock()
*::oInform:FilUnlock()
::oItem:lEnabled:= False
::lSaved:= True
RETURN NIL
ELSEIF nResult == mrOK
DO CASE
CASE ! ::lFromReturn
WITH OBJECT ::oStorage
MsgInfo(:ID)
IF ! :Edit()
MsgSTOP(;
"Î”ÎµÎ½ Î¼Ï€Î¿ÏÎµÎ¯ Î½Î± ÎµÎ½Î·Î¼ÎµÏÏ‰Î¸ÎµÎ¯ Î· Î‘Ï€Î¿Î¸Î®ÎºÎ·."+CRLF+CRLF+;
"DataSet: ::oStorage"+CRLF+;
"Î›ÎµÎ¹Ï„Î¿Ï…ÏÎ³Î¯Î±: EDIT()"+CRLF+;
"MÎÎ¸Î¿Î´Î¿Ï‚: InsertNewMaterial()"+CRLF+;
"Î¦ÏŒÏÎ¼Î±: TForm12"," ÎšÏÎ¯ÏƒÎ¹Î¼Î¿ Î£Ï†Î¬Î»Î¼Î± DataSet: 0020/12")
:FilUnlock()
*::oInform:FilUnlock()
::oItem:lEnabled:= False
RETURN NIL
ELSE
:QNTY:= ::oldPricing[01] //QNTY 3
:LASTP:= ::oldPricing[02] //LASTP 7
:LASTSUP:= ::oldPricing[03] //LASTSUP 8
:PRICE:= ::oldPricing[04] //PRICE 9
ENDIF
* ENHMEÎ¡Î©Î˜Î—ÎšÎ• Î¤ÎŸ DATASET ::oSTORAGE ?
LogDisplay(:ID +CRLF+ALLTRIM(STR(:QNTY))+CRLF+:LastSup+CRLF+Alltrim(Str(:Pr ice)))
<<<< HERE I HAVE THE CORECT VALUES ON DATAFIELDS>>>>>>>
IF ! :Update()

<<<<<when :updated() called without any error none of the corected values writen back to the dataset >>>>>
MsgStop(;
"Î”ÎµÎ½ Î¼Ï€Î¿ÏÎµÎ¯ Î½Î± ÎµÎ½Î·Î¼ÎµÏÏ‰Î¸ÎµÎ¯ Î· Î‘Ï€Î¿Î¸Î®ÎºÎ·."+CRLF+CRLF+;
"DataSet: ::oStorage"+CRLF+;
"Î›ÎµÎ¹Ï„Î¿Ï…ÏÎ³Î¯Î±: Update()"+CRLF+;
"MÎÎ¸Î¿Î´Î¿Ï‚: InsertNewMaterial()"+CRLF+;
"Î¦ÏŒÏÎ¼Î±: TForm12"," ÎšÏÎ¯ÏƒÎ¹Î¼Î¿ Î£Ï†Î¬Î»Î¼Î± DataSet: 0004/12")
:FilUnlock()
*::oInform:FilUnlock()
::oItem:lEnabled:= False
RETURN NIL
ELSE
:FilUnlock()
::oItem:lEnabled:= False
::lSaved:= True
ENDIF
END WITH
ÎŸ "Dionisis Divaris" <info@sgs-soft.gr> ÎÎ³ÏÎ±ÏˆÎµ ÏƒÏ„Î¿ Î¼Î®Î½Ï…Î¼Î± news:[email=4a3d4a7c@svctag-j7w3v3j....]4a3d4a7c@svctag-j7w3v3j....[/email]
Hello Jose
Your code works with March Version but not working with June version .. No error occurs when fielde are updating
but no values writen back to the fields of dataset.
TIA
Dionisis
ÎŸ "José David Angulo" <gerencia@microexpressltda.com> ÎÎ³ÏÎ±ÏˆÎµ ÏƒÏ„Î¿ Î¼Î®Î½Ï…Î¼Î± news:[email=4a3d0818@svctag-j7w3v3j....]4a3d0818@svctag-j7w3v3j....[/email]
Hello, Dionisis,
Adds :Edit()
With Object ::datasetName
:Edit() // It is now necessary
:dataSetFieldName:= anyValue
.....
....
:Update()
End With
José David Angulo Urzola.
Auditoria y Sistemas Ltda.
jose.angulo@auditoriaysistemas.com
Tel. (57) 5-6643022 â€“ 6644555
Cartagena â€“ Colombia
Dionisis Divaris escribió:
Hello Ignacio,Jose
I faced with a bad situation due to the last changes on DataSets. I have an application witch it is a bit before distribution stage and i have the following serious problems:
To update various application datasets i use the folowing methodology
With Object ::datasetName
:dataSetFieldName:= anyValue
.....
....
:Update()
End With
This is not working when compiled with June version of Xailer. When i compiled with March version works as
expected. What this happens and how is possible to avoid this 'bad taste'. I need an answer on this ASAP if it possible due to time frame for distribution.
TIA
Dionisis
--

YouTube · Mensaje por **ignacio** » Lun Jun 22, 2009 10:40 am

Dionisis,
As we said on our blog this is an important change on Datacontrols design.
Even if we fix your problem in record time surely more problems will arise
in the near future, so I suggest yo use the previous version of Xailer 2 for
distribution, at least until a new revision of this latest version of Xailer
is published.
About your problem:
It seems a call to Edit() is missing. Maybe you are using DBF datasets that
do not need the call to Edit, but in any way is highly recommended. BTW you
do not indicate if there is any error or just simply the field values are
not saved.
It will be great If could modify any of the actual Datacontrols samples to
force the error you are having. That way we can surely give you a better
solution.
Best regards,
--
Ignacio Ortiz de Zuniga
Xailer support / Soporte de Xailer
http://www.xailer.com
http://www.xailer.info
"Dionisis Divaris" <info@sgs-soft.gr> escribio en el mensaje
news:[email=4a3cc3ca@svctag-j7w3v3j....]4a3cc3ca@svctag-j7w3v3j....[/email]
> Hello Ignacio,Jose
>
> I faced with a bad situation due to the last changes on DataSets. I have
> an application witch it is a bit before distribution stage and i have the
> following serious problems:
> To update various application datasets i use the folowing methodology
>
> With Object ::datasetName
> :dataSetFieldName:= anyValue
> .....
> ....
> :Update()
> End With
>
> This is not working when compiled with June version of Xailer. When i
> compiled with March version works as
> expected. What this happens and how is possible to avoid this 'bad
> taste'. I need an answer on this ASAP if it possible due to time frame for
> distribution.
>
> TIA
> Dionisis
>
>
>
>

YouTube · Mensaje por **ignacio** » Lun Jun 22, 2009 10:50 am

José David AnguloDionisis,
Looking at your code it seems you are updataing manually this fields:
:QNTY:= ::oldPricing[01] //QNTY 3
:LASTP:= ::oldPricing[02] //LASTP 7
:LASTSUP:= ::oldPricing[03] //LASTSUP 8
:PRICE:= ::oldPricing[04] //PRICE 9
Do those fields have any datacontrol linked with them?
For example, suposse field Dataset:QNTY is linked with a TDBEdit datacontrol on TForm13, when you modify its value manually the record gets changed, but when you call Update() the value receives again the TDBedit datacontrol value. Can be this your problem? In case there is a datacontrol linked with any field you must be aware that its value will be used on the Update operation.
BTW, I wait for a small sample that reproduces your error so I do not need to speculate. TIA.
Regards,
--
Ignacio Ortiz de Zúñiga
Xailer support / Soporte de Xailer
http://www.xailer.com
http://www.xailer.info
"Dionisis Divaris" <info@sgs-soft.gr> escribió en el mensaje news:[email=4a3d5c54@svctag-j7w3v3j....]4a3d5c54@svctag-j7w3v3j....[/email]
To see the problem here is a portion of my coding:
WITH OBJECT TForm13():New(self)
nResult:= :ShowModal()
END WITH
IF nResult == mrCANCEL
::oStorage:FilUnlock()
*::oInform:FilUnlock()
::oItem:lEnabled:= False
::lSaved:= True
RETURN NIL
ELSEIF nResult == mrOK
DO CASE
CASE ! ::lFromReturn
WITH OBJECT ::oStorage
MsgInfo(:ID)
IF ! :Edit()
MsgSTOP(;
"Î”ÎµÎ½ Î¼Ï€Î¿ÏÎµÎ¯ Î½Î± ÎµÎ½Î·Î¼ÎµÏÏ‰Î¸ÎµÎ¯ Î· Î‘Ï€Î¿Î¸Î®ÎºÎ·."+CRLF+CRLF+;
"DataSet: ::oStorage"+CRLF+;
"Î›ÎµÎ¹Ï„Î¿Ï…ÏÎ³Î¯Î±: EDIT()"+CRLF+;
"MÎÎ¸Î¿Î´Î¿Ï‚: InsertNewMaterial()"+CRLF+;
"Î¦ÏŒÏÎ¼Î±: TForm12"," ÎšÏÎ¯ÏƒÎ¹Î¼Î¿ Î£Ï†Î¬Î»Î¼Î± DataSet: 0020/12")
:FilUnlock()
*::oInform:FilUnlock()
::oItem:lEnabled:= False
RETURN NIL
ELSE
:QNTY:= ::oldPricing[01] //QNTY 3
:LASTP:= ::oldPricing[02] //LASTP 7
:LASTSUP:= ::oldPricing[03] //LASTSUP 8
:PRICE:= ::oldPricing[04] //PRICE 9
ENDIF
* ENHMEÎ¡Î©Î˜Î—ÎšÎ• Î¤ÎŸ DATASET ::oSTORAGE ?
LogDisplay(:ID +CRLF+ALLTRIM(STR(:QNTY))+CRLF+:LastSup+CRLF+Alltrim(Str(:Pr ice)))
<<<< HERE I HAVE THE CORECT VALUES ON DATAFIELDS>>>>>>>
IF ! :Update()

<<<<<when :updated() called without any error none of the corected values writen back to the dataset >>>>>
MsgStop(;
"Î”ÎµÎ½ Î¼Ï€Î¿ÏÎµÎ¯ Î½Î± ÎµÎ½Î·Î¼ÎµÏÏ‰Î¸ÎµÎ¯ Î· Î‘Ï€Î¿Î¸Î®ÎºÎ·."+CRLF+CRLF+;
"DataSet: ::oStorage"+CRLF+;
"Î›ÎµÎ¹Ï„Î¿Ï…ÏÎ³Î¯Î±: Update()"+CRLF+;
"MÎÎ¸Î¿Î´Î¿Ï‚: InsertNewMaterial()"+CRLF+;
"Î¦ÏŒÏÎ¼Î±: TForm12"," ÎšÏÎ¯ÏƒÎ¹Î¼Î¿ Î£Ï†Î¬Î»Î¼Î± DataSet: 0004/12")
:FilUnlock()
*::oInform:FilUnlock()
::oItem:lEnabled:= False
RETURN NIL
ELSE
:FilUnlock()
::oItem:lEnabled:= False
::lSaved:= True
ENDIF
END WITH
ÎŸ "Dionisis Divaris" <info@sgs-soft.gr> ÎÎ³ÏÎ±ÏˆÎµ ÏƒÏ„Î¿ Î¼Î®Î½Ï…Î¼Î± news:[email=4a3d4a7c@svctag-j7w3v3j....]4a3d4a7c@svctag-j7w3v3j....[/email]
Hello Jose
Your code works with March Version but not working with June version . No error occurs when fielde are updating
but no values writen back to the fields of dataset.
TIA
Dionisis
ÎŸ "José David Angulo" <gerencia@microexpressltda.com> ÎÎ³ÏÎ±ÏˆÎµ ÏƒÏ„Î¿ Î¼Î®Î½Ï…Î¼Î± news:[email=4a3d0818@svctag-j7w3v3j....]4a3d0818@svctag-j7w3v3j....[/email]
Hello, Dionisis,
Adds :Edit()
With Object ::datasetName
:Edit() // It is now necessary
:dataSetFieldName:= anyValue
.....
....
:Update()
End With
José David Angulo Urzola.
Auditoria y Sistemas Ltda.
jose.angulo@auditoriaysistemas.com
Tel. (57) 5-6643022 â€“ 6644555
Cartagena â€“ Colombia
Dionisis Divaris escribió:
Hello Ignacio,Jose
I faced with a bad situation due to the last changes on DataSets. I have an application witch it is a bit before distribution stage and i have the following serious problems:
To update various application datasets i use the folowing methodology
With Object ::datasetName
:dataSetFieldName:= anyValue
.....
....
:Update()
End With
This is not working when compiled with June version of Xailer. When i compiled with March version works as
expected. What this happens and how is possible to avoid this 'bad taste'. I need an answer on this ASAP if it possible due to time frame for distribution.
TIA
Dionisis
--

Dionisis Divaris · Lun Jun 22, 2009 11:11 am

Hello Ignacio
Here is some additional info for the problem:
In the parent form there are some datacontrols wich linked to the database.
When changes made throught these controls everything works. But when
changes done with code none of the changed values writen back to the file
(here is the main problem, because some changes must be with code, on the
fly).
Hope this info helps.
TIA
DIONSIS
"Ignacio Ortiz de Zuniga" <NoNameToAvoidSpam@xailer.com> wrote in message
news:4a3f435d$[email=1@svctag-j7w3v3j....]1@svctag-j7w3v3j....[/email]
> Dionisis,
>
> As we said on our blog this is an important change on Datacontrols design.
> Even if we fix your problem in record time surely more problems will arise
> in the near future, so I suggest yo use the previous version of Xailer 2
> for distribution, at least until a new revision of this latest version of
> Xailer is published.
>
> About your problem:
>
> It seems a call to Edit() is missing. Maybe you are using DBF datasets
> that do not need the call to Edit, but in any way is highly recommended.
> BTW you do not indicate if there is any error or just simply the field
> values are not saved.
>
> It will be great If could modify any of the actual Datacontrols samples to
> force the error you are having. That way we can surely give you a better
> solution.
>
> Best regards,
>
> --
> Ignacio Ortiz de Zuniga
> Xailer support / Soporte de Xailer
> http://www.xailer.com
> http://www.xailer.info
> "Dionisis Divaris" <info@sgs-soft.gr> escribio en el mensaje
> news:[email=4a3cc3ca@svctag-j7w3v3j....]4a3cc3ca@svctag-j7w3v3j....[/email]
>> Hello Ignacio,Jose
>>
>> I faced with a bad situation due to the last changes on DataSets. I have
>> an application witch it is a bit before distribution stage and i have the
>> following serious problems:
>> To update various application datasets i use the folowing methodology
>>
>> With Object ::datasetName
>> :dataSetFieldName:= anyValue
>> .....
>> ....
>> :Update()
>> End With
>>
>> This is not working when compiled with June version of Xailer. When i
>> compiled with March version works as
>> expected. What this happens and how is possible to avoid this 'bad
>> taste'. I need an answer on this ASAP if it possible due to time frame
>> for distribution.
>>
>> TIA
>> Dionisis
>>
>>
>>
>>
>
>

YouTube · Mensaje por **ignacio** » Lun Jun 22, 2009 5:25 pm

Dionisis,
On previous versions of Xailer, every time you change the value of a
TDataField, the class did look up on all the linked controls to see if any
of them was linked to itself. So when you set a value to a TDatafield,
the linked datacontrol was updated automatically. BTW, this can be very
useful but it can be also a lot of time consuming. In order to improve the
speed we decide to avoid this feature. BTW the fix is really simple, you
only need to change the datacontrol value instead of the datafield value
which I believe is more accurate since on that moment the field is linked to
that datacontrol.
Please I would like to know your point of view about this problem. We may
introduce a property on the TDatafield in order to be compatible with
previous versions of Xailer on this or we may leave it as it was but that
has a great speed penalty.
Waiting for your comments,
Best regards,
--
Ignacio Ortiz de Zúñiga
http://www.xailer.com
http:/xailer.info
"Dionisis Divaris" <info@sgs-soft.gr> escribió en el mensaje de
noticias:4a3f4ab8$[email=1@svctag-j7w3v3j....]1@svctag-j7w3v3j....[/email]
> Hello Ignacio
>
> Here is some additional info for the problem:
> In the parent form there are some datacontrols wich linked to the
> database. When changes made throught these controls everything works. But
> when changes done with code none of the changed values writen back to
> the file (here is the main problem, because some changes must be with
> code, on the fly).
>
> Hope this info helps.
> TIA
> DIONSIS
>
>
> "Ignacio Ortiz de Zuniga" <NoNameToAvoidSpam@xailer.com> wrote in message
> news:4a3f435d$[email=1@svctag-j7w3v3j....]1@svctag-j7w3v3j....[/email]
>> Dionisis,
>>
>> As we said on our blog this is an important change on Datacontrols
>> design. Even if we fix your problem in record time surely more problems
>> will arise in the near future, so I suggest yo use the previous version
>> of Xailer 2 for distribution, at least until a new revision of this
>> latest version of Xailer is published.
>>
>> About your problem:
>>
>> It seems a call to Edit() is missing. Maybe you are using DBF datasets
>> that do not need the call to Edit, but in any way is highly recommended.
>> BTW you do not indicate if there is any error or just simply the field
>> values are not saved.
>>
>> It will be great If could modify any of the actual Datacontrols samples
>> to force the error you are having. That way we can surely give you a
>> better solution.
>>
>> Best regards,
>>
>> --
>> Ignacio Ortiz de Zuniga
>> Xailer support / Soporte de Xailer
>> http://www.xailer.com
>> http://www.xailer.info
>> "Dionisis Divaris" <info@sgs-soft.gr> escribio en el mensaje
>> news:[email=4a3cc3ca@svctag-j7w3v3j....]4a3cc3ca@svctag-j7w3v3j....[/email]
>>> Hello Ignacio,Jose
>>>
>>> I faced with a bad situation due to the last changes on DataSets. I have
>>> an application witch it is a bit before distribution stage and i have
>>> the following serious problems:
>>> To update various application datasets i use the folowing methodology
>>>
>>> With Object ::datasetName
>>> :dataSetFieldName:= anyValue
>>> .....
>>> ....
>>> :Update()
>>> End With
>>>
>>> This is not working when compiled with June version of Xailer. When i
>>> compiled with March version works as
>>> expected. What this happens and how is possible to avoid this 'bad
>>> taste'. I need an answer on this ASAP if it possible due to time frame
>>> for distribution.
>>>
>>> TIA
>>> Dionisis
>>>
>>>
>>>
>>>
>>
>>
>
>

Dionisis Divaris · Lun Jun 22, 2009 7:27 pm

Hello Again Ignacio
I made some changes to the sample DBFData7. Just compile with both Versions
March and June and press the button Simulate problem to see the deferences..
You make clear to me that i can change the values of datacontrols instead of
the datafield it self. But none of all datafields contains datacontrols
linked to them. Please try the sample and speak later. It is very importand
to be able to change all the datafields vallues (those with datacontrols
linked and those without datacontrols linked to them).
Best regards
Dionisis
? "Ignacio Ortiz de Zúñiga" <NoNameToAvoidSpam@xailer.com> ?????? ??? ??????
news:[email=4a3fa269@svctag-j7w3v3j....]4a3fa269@svctag-j7w3v3j....[/email]
> Dionisis,
>
> On previous versions of Xailer, every time you change the value of a
> TDataField, the class did look up on all the linked controls to see if any
> of them was linked to itself. So when you set a value to a TDatafield,
> the linked datacontrol was updated automatically. BTW, this can be very
> useful but it can be also a lot of time consuming. In order to improve the
> speed we decide to avoid this feature. BTW the fix is really simple, you
> only need to change the datacontrol value instead of the datafield value
> which I believe is more accurate since on that moment the field is linked
> to that datacontrol.
>
> Please I would like to know your point of view about this problem. We may
> introduce a property on the TDatafield in order to be compatible with
> previous versions of Xailer on this or we may leave it as it was but that
> has a great speed penalty.
>
> Waiting for your comments,
>
> Best regards,
>
>
> --
> Ignacio Ortiz de Zúñiga
> http://www.xailer.com
> http:/xailer.info
>
> "Dionisis Divaris" <info@sgs-soft.gr> escribió en el mensaje de
> noticias:4a3f4ab8$[email=1@svctag-j7w3v3j....]1@svctag-j7w3v3j....[/email]
>> Hello Ignacio
>>
>> Here is some additional info for the problem:
>> In the parent form there are some datacontrols wich linked to the
>> database. When changes made throught these controls everything works.
>> But
>> when changes done with code none of the changed values writen back to
>> the file (here is the main problem, because some changes must be with
>> code, on the fly).
>>
>> Hope this info helps.
>> TIA
>> DIONSIS
>>
>>
>> "Ignacio Ortiz de Zuniga" <NoNameToAvoidSpam@xailer.com> wrote in message
>> news:4a3f435d$[email=1@svctag-j7w3v3j....]1@svctag-j7w3v3j....[/email]
>>> Dionisis,
>>>
>>> As we said on our blog this is an important change on Datacontrols
>>> design. Even if we fix your problem in record time surely more problems
>>> will arise in the near future, so I suggest yo use the previous version
>>> of Xailer 2 for distribution, at least until a new revision of this
>>> latest version of Xailer is published.
>>>
>>> About your problem:
>>>
>>> It seems a call to Edit() is missing. Maybe you are using DBF datasets
>>> that do not need the call to Edit, but in any way is highly recommended.
>>> BTW you do not indicate if there is any error or just simply the field
>>> values are not saved.
>>>
>>> It will be great If could modify any of the actual Datacontrols samples
>>> to force the error you are having. That way we can surely give you a
>>> better solution.
>>>
>>> Best regards,
>>>
>>> --
>>> Ignacio Ortiz de Zuniga
>>> Xailer support / Soporte de Xailer
>>> http://www.xailer.com
>>> http://www.xailer.info
>>> "Dionisis Divaris" <info@sgs-soft.gr> escribio en el mensaje
>>> news:[email=4a3cc3ca@svctag-j7w3v3j....]4a3cc3ca@svctag-j7w3v3j....[/email]
>>>> Hello Ignacio,Jose
>>>>
>>>> I faced with a bad situation due to the last changes on DataSets. I
>>>> have
>>>> an application witch it is a bit before distribution stage and i have
>>>> the following serious problems:
>>>> To update various application datasets i use the folowing methodology
>>>>
>>>> With Object ::datasetName
>>>> :dataSetFieldName:= anyValue
>>>> .....
>>>> ....
>>>> :Update()
>>>> End With
>>>>
>>>> This is not working when compiled with June version of Xailer. When i
>>>> compiled with March version works as
>>>> expected. What this happens and how is possible to avoid this 'bad
>>>> taste'. I need an answer on this ASAP if it possible due to time frame
>>>> for distribution.
>>>>
>>>> TIA
>>>> Dionisis
>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>
>>
--

Attached files DBFData7.zip (5.5 KB)Â

Ingo JH · Mensaje por **Ingo JH** » Lun Jun 22, 2009 7:47 pm

Ignacio,
I'm using the DataSet-method VarPut() many times in my project after AddNew
when I want to modify the DataControls (i.e. their buffers) in the form with
values from another DataSet without writing these values directly into the
database. I can do it very simple in a for - next loop so the the new values
are shown up in the form.
For example:
//---------------------------------------------------------- --------------------
METHOD BtnBmp1Click( oSender ) CLASS TMP5Edit
LOCAL aR,n,z:=::oMP5:FieldCount()
WITH OBJECT Gerichtsliste():New(self)
IF :ShowModal()=mrOK
aR := :Cargo
ENDIF
:End()
END WITH
IF aR#NIL .AND. LEN(aR)=z
WITH OBJECT ::oMP5
FOR n:=1 TO Z
:VarPut(n,aR[n]) //writing the values only into the buffers of the
Datafields to show them in the form
NEXT
END WITH
ENDIF
RETURN Nil
//---------------------------------------------------------- --------------------
Getting the values from the other DataSet
//---------------------------------------------------------- --------------------
METHOD BtnBmp1Click( oSender ) CLASS Gerichtsliste
LOCAL n,aR,z
WITH OBJECT ::oDbf
z:=:FieldCount()
aR:=ARRAY(z)
FOR n:= 1 TO z
aR[n]:=:FieldGet(n)
NEXT
END WITH
::Cargo:=aR
RETURN Nil
//---------------------------------------------------------- --------------------
As I understand it well - now I have to assign the new values step-by-step
to each DataControl:Value in the form when I don't want to modify the
database itself, isn't it?
Regards
Ingo
"Ignacio Ortiz de Zúñiga" <NoNameToAvoidSpam@xailer.com> schrieb im
Newsbeitrag news:[email=4a3fa269@svctag-j7w3v3j....]4a3fa269@svctag-j7w3v3j....[/email]
> Dionisis,
>
> On previous versions of Xailer, every time you change the value of a
> TDataField, the class did look up on all the linked controls to see if any
> of them was linked to itself. So when you set a value to a TDatafield,
> the linked datacontrol was updated automatically. BTW, this can be very
> useful but it can be also a lot of time consuming. In order to improve the
> speed we decide to avoid this feature. BTW the fix is really simple, you
> only need to change the datacontrol value instead of the datafield value
> which I believe is more accurate since on that moment the field is linked
> to that datacontrol.
>
> Please I would like to know your point of view about this problem. We may
> introduce a property on the TDatafield in order to be compatible with
> previous versions of Xailer on this or we may leave it as it was but that
> has a great speed penalty.
>
> Waiting for your comments,
>
> Best regards,
>
>
> --
> Ignacio Ortiz de Zúñiga
> http://www.xailer.com
> http:/xailer.info
>
> "Dionisis Divaris" <info@sgs-soft.gr> escribió en el mensaje de
> noticias:4a3f4ab8$[email=1@svctag-j7w3v3j....]1@svctag-j7w3v3j....[/email]
>> Hello Ignacio
>>
>> Here is some additional info for the problem:
>> In the parent form there are some datacontrols wich linked to the
>> database. When changes made throught these controls everything works.
>> But
>> when changes done with code none of the changed values writen back to
>> the file (here is the main problem, because some changes must be with
>> code, on the fly).
>>
>> Hope this info helps.
>> TIA
>> DIONSIS
>>
>>
>> "Ignacio Ortiz de Zuniga" <NoNameToAvoidSpam@xailer.com> wrote in message
>> news:4a3f435d$[email=1@svctag-j7w3v3j....]1@svctag-j7w3v3j....[/email]
>>> Dionisis,
>>>
>>> As we said on our blog this is an important change on Datacontrols
>>> design. Even if we fix your problem in record time surely more problems
>>> will arise in the near future, so I suggest yo use the previous version
>>> of Xailer 2 for distribution, at least until a new revision of this
>>> latest version of Xailer is published.
>>>
>>> About your problem:
>>>
>>> It seems a call to Edit() is missing. Maybe you are using DBF datasets
>>> that do not need the call to Edit, but in any way is highly recommended.
>>> BTW you do not indicate if there is any error or just simply the field
>>> values are not saved.
>>>
>>> It will be great If could modify any of the actual Datacontrols samples
>>> to force the error you are having. That way we can surely give you a
>>> better solution.
>>>
>>> Best regards,
>>>
>>> --
>>> Ignacio Ortiz de Zuniga
>>> Xailer support / Soporte de Xailer
>>> http://www.xailer.com
>>> http://www.xailer.info
>>> "Dionisis Divaris" <info@sgs-soft.gr> escribio en el mensaje
>>> news:[email=4a3cc3ca@svctag-j7w3v3j....]4a3cc3ca@svctag-j7w3v3j....[/email]
>>>> Hello Ignacio,Jose
>>>>
>>>> I faced with a bad situation due to the last changes on DataSets. I
>>>> have
>>>> an application witch it is a bit before distribution stage and i have
>>>> the following serious problems:
>>>> To update various application datasets i use the folowing methodology
>>>>
>>>> With Object ::datasetName
>>>> :dataSetFieldName:= anyValue
>>>> .....
>>>> ....
>>>> :Update()
>>>> End With
>>>>
>>>> This is not working when compiled with June version of Xailer. When i
>>>> compiled with March version works as
>>>> expected. What this happens and how is possible to avoid this 'bad
>>>> taste'. I need an answer on this ASAP if it possible due to time frame
>>>> for distribution.
>>>>
>>>> TIA
>>>> Dionisis
>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>
>>

YouTube · Mensaje por **ignacio** » Mié Jun 24, 2009 1:19 pm

Ingo,
On new version of Xailer VarPut() is deprecated, you should use
TDataField:Value or TDataset:FieldPut(). If you are in Edit mode the values
will not be commited until a Update() is done, but their value should be
reflected on any linked datacontrol (within next revision). BTW, I suggest
you set the values directly to the visual datacontrols, instead of the
Tdatafields.
Regards,
--
Ignacio Ortiz de Zúñiga
Xailer support / Soporte de Xailer
http://www.xailer.com
http://www.xailer.info
"Ingo JH" <support@mandantwin.com> escribió en el mensaje
news:[email=4a3fc3c5@svctag-j7w3v3j....]4a3fc3c5@svctag-j7w3v3j....[/email]
> Ignacio,
>
> I'm using the DataSet-method VarPut() many times in my project after
> AddNew when I want to modify the DataControls (i.e. their buffers) in the
> form with values from another DataSet without writing these values
> directly into the database. I can do it very simple in a for - next loop
> so the the new values are shown up in the form.
>
> For example:
>
> //---------------------------------------------------------- --------------------
>
> METHOD BtnBmp1Click( oSender ) CLASS TMP5Edit
> LOCAL aR,n,z:=::oMP5:FieldCount()
> WITH OBJECT Gerichtsliste():New(self)
> IF :ShowModal()=mrOK
> aR := :Cargo
> ENDIF
> :End()
> END WITH
> IF aR#NIL .AND. LEN(aR)=z
> WITH OBJECT ::oMP5
> FOR n:=1 TO Z
> :VarPut(n,aR[n]) //writing the values only into the buffers of the
> Datafields to show them in the form
> NEXT
> END WITH
> ENDIF
> RETURN Nil
>
> //---------------------------------------------------------- --------------------
>
> Getting the values from the other DataSet
> //---------------------------------------------------------- --------------------
>
> METHOD BtnBmp1Click( oSender ) CLASS Gerichtsliste
> LOCAL n,aR,z
> WITH OBJECT ::oDbf
> z:=:FieldCount()
> aR:=ARRAY(z)
> FOR n:= 1 TO z
> aR[n]:=:FieldGet(n)
> NEXT
> END WITH
> ::Cargo:=aR
> RETURN Nil
>
> //---------------------------------------------------------- --------------------
>
> As I understand it well - now I have to assign the new values step-by-step
> to each DataControl:Value in the form when I don't want to modify the
> database itself, isn't it?
>
> Regards
>
> Ingo
>
>
>
> "Ignacio Ortiz de Zúñiga" <NoNameToAvoidSpam@xailer.com> schrieb im
> Newsbeitrag news:[email=4a3fa269@svctag-j7w3v3j....]4a3fa269@svctag-j7w3v3j....[/email]
>> Dionisis,
>>
>> On previous versions of Xailer, every time you change the value of a
>> TDataField, the class did look up on all the linked controls to see if
>> any
>> of them was linked to itself. So when you set a value to a TDatafield,
>> the linked datacontrol was updated automatically. BTW, this can be very
>> useful but it can be also a lot of time consuming. In order to improve
>> the speed we decide to avoid this feature. BTW the fix is really simple,
>> you only need to change the datacontrol value instead of the datafield
>> value which I believe is more accurate since on that moment the field is
>> linked to that datacontrol.
>>
>> Please I would like to know your point of view about this problem. We may
>> introduce a property on the TDatafield in order to be compatible with
>> previous versions of Xailer on this or we may leave it as it was but that
>> has a great speed penalty.
>>
>> Waiting for your comments,
>>
>> Best regards,
>>
>>
>> --
>> Ignacio Ortiz de Zúñiga
>> http://www.xailer.com
>> http:/xailer.info
>>
>> "Dionisis Divaris" <info@sgs-soft.gr> escribió en el mensaje de
>> noticias:4a3f4ab8$[email=1@svctag-j7w3v3j....]1@svctag-j7w3v3j....[/email]
>>> Hello Ignacio
>>>
>>> Here is some additional info for the problem:
>>> In the parent form there are some datacontrols wich linked to the
>>> database. When changes made throught these controls everything works.
>>> But
>>> when changes done with code none of the changed values writen back to
>>> the file (here is the main problem, because some changes must be with
>>> code, on the fly).
>>>
>>> Hope this info helps.
>>> TIA
>>> DIONSIS
>>>
>>>
>>> "Ignacio Ortiz de Zuniga" <NoNameToAvoidSpam@xailer.com> wrote in
>>> message
>>> news:4a3f435d$[email=1@svctag-j7w3v3j....]1@svctag-j7w3v3j....[/email]
>>>> Dionisis,
>>>>
>>>> As we said on our blog this is an important change on Datacontrols
>>>> design. Even if we fix your problem in record time surely more problems
>>>> will arise in the near future, so I suggest yo use the previous version
>>>> of Xailer 2 for distribution, at least until a new revision of this
>>>> latest version of Xailer is published.
>>>>
>>>> About your problem:
>>>>
>>>> It seems a call to Edit() is missing. Maybe you are using DBF datasets
>>>> that do not need the call to Edit, but in any way is highly
>>>> recommended.
>>>> BTW you do not indicate if there is any error or just simply the field
>>>> values are not saved.
>>>>
>>>> It will be great If could modify any of the actual Datacontrols samples
>>>> to force the error you are having. That way we can surely give you a
>>>> better solution.
>>>>
>>>> Best regards,
>>>>
>>>> --
>>>> Ignacio Ortiz de Zuniga
>>>> Xailer support / Soporte de Xailer
>>>> http://www.xailer.com
>>>> http://www.xailer.info
>>>> "Dionisis Divaris" <info@sgs-soft.gr> escribio en el mensaje
>>>> news:[email=4a3cc3ca@svctag-j7w3v3j....]4a3cc3ca@svctag-j7w3v3j....[/email]
>>>>> Hello Ignacio,Jose
>>>>>
>>>>> I faced with a bad situation due to the last changes on DataSets. I
>>>>> have
>>>>> an application witch it is a bit before distribution stage and i have
>>>>> the following serious problems:
>>>>> To update various application datasets i use the folowing methodology
>>>>>
>>>>> With Object ::datasetName
>>>>> :dataSetFieldName:= anyValue
>>>>> .....
>>>>> ....
>>>>> :Update()
>>>>> End With
>>>>>
>>>>> This is not working when compiled with June version of Xailer. When i
>>>>> compiled with March version works as
>>>>> expected. What this happens and how is possible to avoid this 'bad
>>>>> taste'. I need an answer on this ASAP if it possible due to time frame
>>>>> for distribution.
>>>>>
>>>>> TIA
>>>>> Dionisis
>>>>>
>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>
>>>
>