Documentation suggests to subclass VDatabase and VTable as a preferred design pattern (Articles/Choosing a Style of Coding). Since the only way to get a VTable instance is to use the .table method of the factory class VDatabase I don't see any possibility to get a subclass of VTable that is connected to the database server.
Class myDatabase As VDatabase …
Class myTable As VTable …
myTable = myDatabase.table("tableName"
If I override the .table method in myDatabase it will generate an empty subclass of VTable. If I don't it will throw a cast exception, since a superclass can't be downcasted to it's subclass. Did I miss here something?
I would very much appreciate any suggestions for a best practice to implement application specific code based on the Valentina classes.