We are attempting to upgrade from ver 5 to ver 10.5. The conversion is going well, now, however there seems to be an issue with the shadow databases. Our "system" s structured in a way where we have a main, "Calling" database at the root of our server's shared drive. The "called" databases reside in subfolders under this root location. Some of our sub databases use tables that reside in other folders as the tables are "shared" among many different databases.
Example: Customer information tables reside in a folder: "g:\casereg". they contain demographic and case information pertaining to our customers. Our Medicaid database resides in a folder: "g:\medicaid". Information in medicaid is linked to the customer tables. The customer tables are included in the medicaid database and the path shows appropriately.
In our "live" ver 5 system, the shadow folder mirrored the shared folder on our server, ie; the shared drive "g" was at the uppermost level of our shadow folder. Customer information files were in the folder "shadow\casereg", and medicaid files were in "shadow\medicaid". The customer information database was in the casereg folder and the medicaid database was in the medicaid folder. The Medicaid database, which containes customer information tables and sets correctly points to the "shadow\casereg" folder for its pointer to the customer information tables.
In ver 10.5, all tables in the databses get placed into subfolders of the database main folder. Customer information tables used in Medicaid now show a path of "shadow\medicaid\casereg" .
I realize that many don't have a situation where one database calls another and so on, or where databases share information across subfolder boundries, but if anyone has any ideas as to how to resolve this without telling me to create one gigantic database, I will be glad to know.
Thanks,
Tom
Example: Customer information tables reside in a folder: "g:\casereg". they contain demographic and case information pertaining to our customers. Our Medicaid database resides in a folder: "g:\medicaid". Information in medicaid is linked to the customer tables. The customer tables are included in the medicaid database and the path shows appropriately.
In our "live" ver 5 system, the shadow folder mirrored the shared folder on our server, ie; the shared drive "g" was at the uppermost level of our shadow folder. Customer information files were in the folder "shadow\casereg", and medicaid files were in "shadow\medicaid". The customer information database was in the casereg folder and the medicaid database was in the medicaid folder. The Medicaid database, which containes customer information tables and sets correctly points to the "shadow\casereg" folder for its pointer to the customer information tables.
In ver 10.5, all tables in the databses get placed into subfolders of the database main folder. Customer information tables used in Medicaid now show a path of "shadow\medicaid\casereg" .
I realize that many don't have a situation where one database calls another and so on, or where databases share information across subfolder boundries, but if anyone has any ideas as to how to resolve this without telling me to create one gigantic database, I will be glad to know.
Thanks,
Tom
Comment