Xailer & OZ Software

Here's my code:
if MsgCancelOk("Delete selected record?")
::oDBFDataSetApplications:Delete()
::oDBFDataSetApplications:UpDateControls()
// ::oDBBrowseApplications:Refresh()
endif
I can confirm in DBF Explore that the record has been deleted, yet it still
displays in the DBBrowse and in the other data controls on the form. I have
SET DELETED ON, so I don't know what's going on here. For test purposes,
there is just one record in the database and the database is not indexed.
With linked controls, I don't know that it is necessary to issue the
UpDatecontrols() or the Refresh(), but I tried them just to see if it made a
difference.
TIA,
Gary

Gary,
TDbfDataset:Delete() should be the only code you should need. Please take a
look at samplesDbfDatacontrolsDbfData2 or tell us how to reproduce your
error with that sample. TIA.
Regards,
--
Ignacio Ortiz de Zúñiga
Xailer support / Soporte de Xailer
http://www.xailer.com
http://www.xailer.info
"Gary S. Rogers" <g.s.rogers@att.net> escribió en el mensaje
news:4990963c$[email=1@svctag-j7w3v3j....]1@svctag-j7w3v3j....[/email]
> Here's my code:
>
> if MsgCancelOk("Delete selected record?")
> ::oDBFDataSetApplications:Delete()
> ::oDBFDataSetApplications:UpDateControls()
> // ::oDBBrowseApplications:Refresh()
> endif
>
> I can confirm in DBF Explore that the record has been deleted, yet it
> still displays in the DBBrowse and in the other data controls on the form.
> I have SET DELETED ON, so I don't know what's going on here. For test
> purposes, there is just one record in the database and the database is not
> indexed. With linked controls, I don't know that it is necessary to issue
> the UpDatecontrols() or the Refresh(), but I tried them just to see if it
> made a difference.
>
> TIA,
> Gary
>
>

Gary,
TDbfDataset:Delete() should be the only code you should need. Please take a
look at samplesDbfDatacontrolsDbfData2 or tell us how to reproduce your
error with that sample. TIA.
Regards,
--
Ignacio Ortiz de Zúñiga
Xailer support / Soporte de Xailer
http://www.xailer.com
http://www.xailer.info
"Gary S. Rogers" <g.s.rogers@att.net> escribió en el mensaje
news:4990963c$[email=1@svctag-j7w3v3j....]1@svctag-j7w3v3j....[/email]
> Here's my code:
>
> if MsgCancelOk("Delete selected record?")
> ::oDBFDataSetApplications:Delete()
> ::oDBFDataSetApplications:UpDateControls()
> // ::oDBBrowseApplications:Refresh()
> endif
>
> I can confirm in DBF Explore that the record has been deleted, yet it
> still displays in the DBBrowse and in the other data controls on the form.
> I have SET DELETED ON, so I don't know what's going on here. For test
> purposes, there is just one record in the database and the database is not
> indexed. With linked controls, I don't know that it is necessary to issue
> the UpDatecontrols() or the Refresh(), but I tried them just to see if it
> made a difference.
>
> TIA,
> Gary
>
>

I found that if I issued the command SET DELETED ON in a starter program
which then called the main form, the SET DELETED ON had no effect. I had to
put the SET DELETED ON in the initialization event of the form. Perhaps this
is related to the fact that the dataset is opened in the called form, not in
the starter program. I was under the impression that commands like SET
DELETED ON were system-wide, not just module specific.
Gary
"Gary S. Rogers" <g.s.rogers@att.net> wrote in message
news:4990963c$[email=1@svctag-j7w3v3j....]1@svctag-j7w3v3j....[/email]
> Here's my code:
>
> if MsgCancelOk("Delete selected record?")
> ::oDBFDataSetApplications:Delete()
> ::oDBFDataSetApplications:UpDateControls()
> // ::oDBBrowseApplications:Refresh()
> endif
>
> I can confirm in DBF Explore that the record has been deleted, yet it
> still displays in the DBBrowse and in the other data controls on the form.
> I have SET DELETED ON, so I don't know what's going on here. For test
> purposes, there is just one record in the database and the database is not
> indexed. With linked controls, I don't know that it is necessary to issue
> the UpDatecontrols() or the Refresh(), but I tried them just to see if it
> made a difference.
>
> TIA,
> Gary
>

I found that if I issued the command SET DELETED ON in a starter program
which then called the main form, the SET DELETED ON had no effect. I had to
put the SET DELETED ON in the initialization event of the form. Perhaps this
is related to the fact that the dataset is opened in the called form, not in
the starter program. I was under the impression that commands like SET
DELETED ON were system-wide, not just module specific.
Gary
"Gary S. Rogers" <g.s.rogers@att.net> wrote in message
news:4990963c$[email=1@svctag-j7w3v3j....]1@svctag-j7w3v3j....[/email]
> Here's my code:
>
> if MsgCancelOk("Delete selected record?")
> ::oDBFDataSetApplications:Delete()
> ::oDBFDataSetApplications:UpDateControls()
> // ::oDBBrowseApplications:Refresh()
> endif
>
> I can confirm in DBF Explore that the record has been deleted, yet it
> still displays in the DBBrowse and in the other data controls on the form.
> I have SET DELETED ON, so I don't know what's going on here. For test
> purposes, there is just one record in the database and the database is not
> indexed. With linked controls, I don't know that it is necessary to issue
> the UpDatecontrols() or the Refresh(), but I tried them just to see if it
> made a difference.
>
> TIA,
> Gary
>

Gary,
Of course is how you presume, Xailer DBF datasets follows the rules of any
SET statement.
The fact that SET DELETED is ON does not mean you can not directly navigate
to a deleted record. Is a good practice to perform a GOTOP after an DBF
fileopen just to be sure the record pointer is not on a deleted record.
BTW, if you still think that is our problem I would highly appreciate if you
could send us a small sample that shows it.
Regards,
--
Ignacio Ortiz de Zúñiga
Xailer support / Soporte de Xailer
http://www.xailer.com
http://www.xailer.info
"Gary S. Rogers" <g.s.rogers@att.net> escribió en el mensaje
news:[email=4995b8eb@svctag-j7w3v3j....]4995b8eb@svctag-j7w3v3j....[/email]
>I found that if I issued the command SET DELETED ON in a starter program
>which then called the main form, the SET DELETED ON had no effect. I had to
>put the SET DELETED ON in the initialization event of the form. Perhaps
>this is related to the fact that the dataset is opened in the called form,
>not in the starter program. I was under the impression that commands like
>SET DELETED ON were system-wide, not just module specific.
>
> Gary
>
>
> "Gary S. Rogers" <g.s.rogers@att.net> wrote in message
> news:4990963c$[email=1@svctag-j7w3v3j....]1@svctag-j7w3v3j....[/email]
>> Here's my code:
>>
>> if MsgCancelOk("Delete selected record?")
>> ::oDBFDataSetApplications:Delete()
>> ::oDBFDataSetApplications:UpDateControls()
>> // ::oDBBrowseApplications:Refresh()
>> endif
>>
>> I can confirm in DBF Explore that the record has been deleted, yet it
>> still displays in the DBBrowse and in the other data controls on the
>> form. I have SET DELETED ON, so I don't know what's going on here. For
>> test purposes, there is just one record in the database and the database
>> is not indexed. With linked controls, I don't know that it is necessary
>> to issue the UpDatecontrols() or the Refresh(), but I tried them just to
>> see if it made a difference.
>>
>> TIA,
>> Gary
>>
>
>

Gary,
Of course is how you presume, Xailer DBF datasets follows the rules of any
SET statement.
The fact that SET DELETED is ON does not mean you can not directly navigate
to a deleted record. Is a good practice to perform a GOTOP after an DBF
fileopen just to be sure the record pointer is not on a deleted record.
BTW, if you still think that is our problem I would highly appreciate if you
could send us a small sample that shows it.
Regards,
--
Ignacio Ortiz de Zúñiga
Xailer support / Soporte de Xailer
http://www.xailer.com
http://www.xailer.info
"Gary S. Rogers" <g.s.rogers@att.net> escribió en el mensaje
news:[email=4995b8eb@svctag-j7w3v3j....]4995b8eb@svctag-j7w3v3j....[/email]
>I found that if I issued the command SET DELETED ON in a starter program
>which then called the main form, the SET DELETED ON had no effect. I had to
>put the SET DELETED ON in the initialization event of the form. Perhaps
>this is related to the fact that the dataset is opened in the called form,
>not in the starter program. I was under the impression that commands like
>SET DELETED ON were system-wide, not just module specific.
>
> Gary
>
>
> "Gary S. Rogers" <g.s.rogers@att.net> wrote in message
> news:4990963c$[email=1@svctag-j7w3v3j....]1@svctag-j7w3v3j....[/email]
>> Here's my code:
>>
>> if MsgCancelOk("Delete selected record?")
>> ::oDBFDataSetApplications:Delete()
>> ::oDBFDataSetApplications:UpDateControls()
>> // ::oDBBrowseApplications:Refresh()
>> endif
>>
>> I can confirm in DBF Explore that the record has been deleted, yet it
>> still displays in the DBBrowse and in the other data controls on the
>> form. I have SET DELETED ON, so I don't know what's going on here. For
>> test purposes, there is just one record in the database and the database
>> is not indexed. With linked controls, I don't know that it is necessary
>> to issue the UpDatecontrols() or the Refresh(), but I tried them just to
>> see if it made a difference.
>>
>> TIA,
>> Gary
>>
>
>