For some reason Paradox refused to open up any files that were longer than the 8.3 file name (old DOS Win 3.11 format) or any file name with spaces in it. You will also need to update the Working Directory in Paradox and the NET DIR in BDEADMIN to reflect the new move.įinally I had serious problems with a move to 2012 Server. Click Yes and point to the new location and save your form. When opening the form you be prompted that the file is no longer there and do you wish to use another table. When editing forms again it uses absolute file locations for the tables and these will also be broken. You need to edit the table and use the space bar to put an * back in the field that is the key field. Once you have copied the files you will need to re-establish these relationships and note that any fields defined as an incremental Key field will no longer be incremental key fields after the copy. The referential integrity and PK-FK links are stored as an absolute file location so moving them from C: to E: will break them all. You will need to map these down as these will all be broken when you move the files to a new location. It is here you can view and set the PF-FK relationship as well as the referential integrity relationships. On the left hand side you have the fields and on the right hand side you have a table properties drop down. To do this open the Project Viewer and right click on each original table and choose Info Structure, In here you will need to check for the establish PK-FK relationships that are defined in the Data Model files stored separately). To my knowledge there is no visual tool that maps out the entire relational structure so this has to be done manually. The first thing you need to do is examine all tables and see how the related to each other. When moving a database to a new file server it is not a simple matter of just copying the files. There is no database engine that handles database components. Tables, data models, forms (views), queries etc. are physical files within directories. The most pertinent point to remember about Corel Paradox is that is a file based database. If you are like me and inherited an old Paradox system then you might find this article of some help. This post is to share some experiences and frustrations I’ve had while moving a Corel Paradox database from a Windows 2003 server to Windows 2012 file server.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |