Encapsulating Geodatabase Classes
Getting frustrated with VB’s lack of “Object-Orientated”ness I’ve begun to create a few simple classes to encapsulate things that are often needed when manipulating objects relating to (Personal) Geodatabases (Access dbs). For example, my FeatureClass class is intended to provide the associated Workspace and Dataset and also the Name, WorkspaceName, DatasetName and FeatureClassName. I expect these to be of most use during initial design work. They are still in development and I’d welcome constructive criticism.
The advantages to this approach, if advantages there be, are demonstrated in the “CopyFeatureDataset” and “ConvertFeatureClass” subroutines in comparison with the original samples.