Home > Articles > Programming > Visual Basic

  • Print
  • + Share This

Property Bags

Property bags have the following characteristics:

  • Performance: Good

  • Object-Oriented: Yes

  • Self-Defined: No

Using property bags as a transport emerged along with the inclusion of object persistence in Visual Basic 6.0. Property bag objects can contain an entire instance of any object and convert that object to a byte array. The byte array can than be moved across process boundaries as a return value from a function. Once it's received by a calling client, the byte array is fed back into a property bag to re-create the object.

In many ways, using a property bag is the same as using MSPersist to pass Recordsets across process boundaries. The difference is that a property bag can convert any object into a byte array. The attraction of this approach is that you can build and pass custom objects like customer, order, and supplier objects. Because you can actually pass objects that represent business entities, many developers feel this approach is the closest to a pure OO application; however, it can be cumbersome to program and somewhat inflexible.

New Versus CreateObject

When using the property bag approach, you might often find that you are creating instances of custom objects within the same DLL. This raises the issue of whether to use the New keyword or the CreateObject function when instancing your objects. This issue has implications for all objects in your system, so I discuss it here.

Although using the New keyword in a COM+ application is acceptable, you must be aware of some limitations. When you create instances with the New keyword and the creator is in the same DLL as the class being instantiated, Visual Basic creates the instance through an optimized process known only to VB. This is a problem because COM+ can't set up properly when instances are created this way.

The New keyword can be used anytime when the creator is in a different DLL from the class being instantiated. In this case, the New keyword evokes the normal creation process and COM+ works just fine. I have seen many developers misunderstand these limitations. In some cases, development teams have gone through their entire application and replaced New with CreateObject. My experience, on the other hand, is that well-designed distributed systems generally have no need to create instances of classes within the DLL. They generally are looking for services from a separate component.

Nonetheless, be aware of this limitation and watch for it in code reviews.

Before you can even begin to use this transport mechanism, you must understand how to achieve object persistence in Visual Basic. Beginning with Visual Basic 6.0, you could create a persistent object by setting the Persistable property in a class module. The typical scheme is to create a class module that maps to a business entity and then make the class persistable.

When a class module is designated as persistable, Visual Basic adds three new events to the class: InitProperties, ReadProperties, and WriteProperties. The class is also now associated with a PropertyBag object that enables the persistence. The idea here is to save the values from a recordset into the class properties.

The PropertyBag object can hold the values of the properties in the class to be persisted. To store values in the PropertyBag, the class must explicitly read and write them to the bag. Reading and writing properties must occur in the ReadProperties and WriteProperties events. The code in Listing 4 shows how a class module representing an author might manage properties with a PropertyBag object.

Listing 4: Managing Properties with a Property Bag

Private Sub Class_ReadProperties(PropBag As PropertyBag)
    With PropBag
        m_au_id = .ReadProperty("au_id")
        m_au_fname = .ReadProperty("au_fname")
        m_au_lname = .ReadProperty("au_lname")
        m_address = .ReadProperty("address")
        m_city = .ReadProperty("city")
        m_state = .ReadProperty("state")
        m_zip = .ReadProperty("zip")
    End With
End Sub

Private Sub Class_WriteProperties(PropBag As PropertyBag)
    With PropBag
        .WriteProperty "au_id", m_au_id
        .WriteProperty "au_fname", m_au_fname
        .WriteProperty "au_lname", m_au_lname
        .WriteProperty "address", m_address
        .WriteProperty "city", m_city
        .WriteProperty "state", m_state
        .WriteProperty "zip", m_zip
    End With
End Sub

When the object has persistence behavior, a separate PropertyBag can be used to create a byte array that represents the contents of the property bag. It's the array that can be transferred efficiently across process boundaries. Listing 5 shows how the same author object can be filled from a firehose cursor, changed into a byte array, and transferred to a calling client.

Listing 5: Returning a Byte Array

Public Function GetAuthor(ByVal strSSN As String) As Byte()

'This function returns a byte array
'from a property bag

On Error GoTo GetAuthorsErr

    Dim objRecordset As ADODB.Recordset
    Dim objAuthor As ByteTrans.Author
    Dim objBag As PropertyBag

    'Run Query
    Set objRecordset = New ADODB.Recordset
    objRecordset.Open _
    "SELECT * FROM Authors WHERE au_id ='" & strSSN & "'", _
    "Provider=SQLOLEDB;Data Source=(local);Initial Catalog=pubs;UID=sa;PWD=;" _
    , adOpenForwardOnly, adLockReadOnly

    'Create Author object
    'NOTE: Use CreateObject because the are in the same DLL!
    Set objAuthor = CreateObject("ByteTrans.Author")

    'Fill object from Recordset
    With objAuthor
        .au_id = objRecordset!au_id
        .au_fname = objRecordset!au_fname
        .au_lname = objRecordset!au_lname
        .address = objRecordset!address
        .city = objRecordset!city
        .state = objRecordset!state
        .zip = objRecordset!zip
    End With

    Set objRecordset = Nothing

    'Put object in Property Bag
    Set objBag = New PropertyBag
    objBag.WriteProperty "Author", objAuthor

    'Return Byte Array
    GetAuthor = objBag.Contents

    Exit Function

    Debug.Print Err.Description
    Resume GetAuthorsExit
End Function

After the byte array is transferred to the calling client, a new property bag can be used to reconstitute the original object. This has the effect of allowing you to pass custom objects in your system without the overhead of marshaling. The following code shows how to re-create the same author object in the client process:

'Call Data Layer
bytData = objData.GetAuthor(txtSSN)
objBag.Contents = bytData

'Re-create Author Object
Set objAuthor = objBag.ReadProperty("Author")
  • + Share This
  • 🔖 Save To Your Account

InformIT Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from InformIT and its family of brands. I can unsubscribe at any time.


Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about products and services that can be purchased through this site.

This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies.

Collection and Use of Information

To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including:

Questions and Inquiries

For inquiries and questions, we collect the inquiry or question, together with name, contact details (email address, phone number and mailing address) and any other additional information voluntarily submitted to us through a Contact Us form or an email. We use this information to address the inquiry and respond to the question.

Online Store

For orders and purchases placed through our online store on this site, we collect order details, name, institution name and address (if applicable), email address, phone number, shipping and billing addresses, credit/debit card information, shipping options and any instructions. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.


Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites, develop new products and services, conduct educational research and for other purposes specified in the survey.

Contests and Drawings

Occasionally, we may sponsor a contest or drawing. Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law.


If you have elected to receive email newsletters or promotional mailings and special offers but want to unsubscribe, simply email information@informit.com.

Service Announcements

On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email. Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature.

Customer Service

We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our Contact Us form.

Other Collection and Use of Information

Application and System Logs

Pearson automatically collects log data to help ensure the delivery, availability and security of this site. Log data may include technical information about how a user or visitor connected to this site, such as browser type, type of computer/device, operating system, internet service provider and IP address. We use this information for support purposes and to monitor the health of the site, identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents and appropriately scale computing resources.

Web Analytics

Pearson may use third party web trend analytical services, including Google Analytics, to collect visitor information, such as IP addresses, browser types, referring pages, pages visited and time spent on a particular site. While these analytical services collect and report information on an anonymous basis, they may use cookies to gather web trend information. The information gathered may enable Pearson (but not the third party web trend services) to link information with application and system log data. Pearson uses this information for system administration and to identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents, appropriately scale computing resources and otherwise support and deliver this site and its services.

Cookies and Related Technologies

This site uses cookies and similar technologies to personalize content, measure traffic patterns, control security, track use and access of information on this site, and provide interest-based messages and advertising. Users can manage and block the use of cookies through their browser. Disabling or blocking certain cookies may limit the functionality of this site.

Do Not Track

This site currently does not respond to Do Not Track signals.


Pearson uses appropriate physical, administrative and technical security measures to protect personal information from unauthorized access, use and disclosure.


This site is not directed to children under the age of 13.


Pearson may send or direct marketing communications to users, provided that

  • Pearson will not use personal information collected or processed as a K-12 school service provider for the purpose of directed or targeted advertising.
  • Such marketing is consistent with applicable law and Pearson's legal obligations.
  • Pearson will not knowingly direct or send marketing communications to an individual who has expressed a preference not to receive marketing.
  • Where required by applicable law, express or implied consent to marketing exists and has not been withdrawn.

Pearson may provide personal information to a third party service provider on a restricted basis to provide marketing solely on behalf of Pearson or an affiliate or customer for whom Pearson is a service provider. Marketing preferences may be changed at any time.

Correcting/Updating Personal Information

If a user's personally identifiable information changes (such as your postal address or email address), we provide a way to correct or update that user's personal data provided to us. This can be done on the Account page. If a user no longer desires our service and desires to delete his or her account, please contact us at customer-service@informit.com and we will process the deletion of a user's account.


Users can always make an informed choice as to whether they should proceed with certain services offered by InformIT. If you choose to remove yourself from our mailing list(s) simply visit the following page and uncheck any communication you no longer want to receive: www.informit.com/u.aspx.

Sale of Personal Information

Pearson does not rent or sell personal information in exchange for any payment of money.

While Pearson does not sell personal information, as defined in Nevada law, Nevada residents may email a request for no sale of their personal information to NevadaDesignatedRequest@pearson.com.

Supplemental Privacy Statement for California Residents

California residents should read our Supplemental privacy statement for California residents in conjunction with this Privacy Notice. The Supplemental privacy statement for California residents explains Pearson's commitment to comply with California law and applies to personal information of California residents collected in connection with this site and the Services.

Sharing and Disclosure

Pearson may disclose personal information, as follows:

  • As required by law.
  • With the consent of the individual (or their parent, if the individual is a minor)
  • In response to a subpoena, court order or legal process, to the extent permitted or required by law
  • To protect the security and safety of individuals, data, assets and systems, consistent with applicable law
  • In connection the sale, joint venture or other transfer of some or all of its company or assets, subject to the provisions of this Privacy Notice
  • To investigate or address actual or suspected fraud or other illegal activities
  • To exercise its legal rights, including enforcement of the Terms of Use for this site or another contract
  • To affiliated Pearson companies and other companies and organizations who perform work for Pearson and are obligated to protect the privacy of personal information consistent with this Privacy Notice
  • To a school, organization, company or government agency, where Pearson collects or processes the personal information in a school setting or on behalf of such organization, company or government agency.


This web site contains links to other sites. Please be aware that we are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of each and every web site that collects Personal Information. This privacy statement applies solely to information collected by this web site.

Requests and Contact

Please contact us about this Privacy Notice or if you have any requests or questions relating to the privacy of your personal information.

Changes to this Privacy Notice

We may revise this Privacy Notice through an updated posting. We will identify the effective date of the revision in the posting. Often, updates are made to provide greater clarity or to comply with changes in regulatory requirements. If the updates involve material changes to the collection, protection, use or disclosure of Personal Information, Pearson will provide notice of the change through a conspicuous notice on this site or other appropriate way. Continued use of the site after the effective date of a posted revision evidences acceptance. Please contact us if you have questions or concerns about the Privacy Notice or any objection to any revisions.

Last Update: November 17, 2020