FastAccess Example:

        Do you meet a giant table? If so, you may be asked to improve data accessing speed. OleDBPro supports all the common ways to increase performance, such as batch records fetching, batch records writing, bookmarking (Scroll), record scrolling (Scroll), and use of indexes and keys (Indexes and FilterSort). This example introduces you a unique way to reduce data movement over network. The resultant improvement is dependent on both what percentage of fetching data is avoided and if a provider sets the property DBPROPSET_DEFERRED to true by default. For the details of ideas, click here.

        It is notified that most of providers don't support this property or set it true by default, but you can still use this way to code your application safely. We can't predict if your OLEDB provider will set this property to true by default in the future, but your codes will automatically increase the data accessing speed if you use it now and your OLEDB provider does so. We encourage you to test this feature with MS Jet providers and a big table as shown in this example.

        This example shows you the following how-tos:

1. How to use CRBase::SetDBPart(ULONG nCol, DBPART nDBPart=DBPART_LENGTH|DBPART_VALUE|DBPART_STATUS) to modify a underlying DBBINDING structure at run time.

2. How to use this function to discard and regain fields at run time according to your needs and situations, which is one of the best ways to improve the management of your data.

3. How to use CRBase::GetDataEx and CRBase::SetDataEx to retrieve and update data from and into the discarded fields.

Goto the list of examples