This issue occurs only when upgrading from a v3.x version to v4.1 as database types are changed in v4.x (from mdb to vdb4)
However there won't be any issues when upgrading from v4.0 to v4.1 (both use vdb4).
So only when upgrading from a v3.x version to v4.1, this extra step is required when following the
upgrade instructions:
In step 5, copy FileVista.vdb4 file from this zip (v4.0) to the existing App_Data\database folder:
FileVista v4.0This upgrade issue will be fixed in v4.2 so that the extra step is not required.