What exactly are you trying to achieve? Do you want to ensure that after an insert your object was actually saved in your data store?
In any case, you would normally use the Exists command before you load the data of an entry for which you have an ID. This could be done if you dont trust the data in the store you are retreiving from (e.g. you could be returning the data from a database you dont really have control over) but there are many other uses for it (or other commandbase objects).
One place you can use it is when you are on a screen and need to know if the user input ID exists in the DB or not so you can branch your code to Fetch the existing ID that is in the DB or else create a New Bo using DP_Create.
e.g.
If MyBO.Exists("someID") Then
MyBO.FetchBO("someID")
Else
MyBO.NewBO("someID")
End If
Just to add
The commandbase was also designed to run query which involves a lot of records and just to return one record.
Let say Property of TotalAmount in Order object will need to fetch all invoice items to the client and summate them which not performance effective right just just write a commandbase object and let the database server do calculation and just get the total
Copyright (c) Marimer LLC