Each time you create the object,
Access assigns it a unique name to distinguish it from other instances of the object. In other words,
a single Access program can host more than one instance of the object, each object operating independently
of the others (possibly even cooperating with the other objects), and maintaining its
own set of properties and other data.
For example, say the Northwind Traders database (included with Microsoft Access) contains a
Product object. The class module supporting the Product object defines the Name, Supplier,
UnitPrice, and other properties of the product. There are any number of Product objects in
the Northwind Traders database, each with its own name, price, and supplier.
To carry the analogy further, another class module might define a ProductInventory collection
object that contains a number of Product objects. The ProductInventory class would
feature a Count property that tells you how many Product objects are in the collection. The
ProductInventory class module might contain a Sell method that deducts a certain
Product item from the ProductInventory.
Pages:
1929
1930
1931
1932
1933
1934
1935
1936
1937
1938
1939
1940
1941
1942
1943
1944
1945
1946
1947
1948
1949
1950
1951
1952
1953