FmPro Migrator - Access To FileMaker Migration Procedure
FmPro Migrator - Access toFileMaker MigrationProcedure
FmPro Migrator - Access to FileMaker Migration Procedure1Overview1.1232.1Office 365 Compatibility Problem2.2Step 1 - Get Info - Access to FileMaker Pro112.3Install FileMaker ODBC Driver - macOS (FileMaker 7,8,910)162.4Install FileMaker ODBC Driver - macOS (FileMaker 11 )252.5Install FileMaker ODBC Driver - Windows - FileMaker 7,8,9,10402.6Install FileMaker ODBC Driver - Windows - FileMaker 11 467Step 2Step 2 - Create Tables55Step 34.155Step 13.14OverviewStep 3 - Transfer Data - Access to FileMaker Pro61Migrating Forms/Reports, Relationships, Value Lists & Visual Basic Code5.1AccessDDRExport - Extracting Info From Access (FileMaker Pro Migration)675.2Using Demo Mode - Access to FmPro775.3Using Licensed Mode - Access to FmPro815.4Creating TOs - Access to FmPro865.5Creating Relationships - Access to FmPro895.6Creating Value Lists - Access to FmPro915.7Creating FileMaker Scripts from Visual Basic Code - Access to FmPro975.8Creating Layouts - Access to FmPro100
6Manual Completion Tasks6.1Manual Tasks - Access to FmPro106
OverviewFmPro Migrator - Access to FileMaker Migration Procedure - 4
OverviewThis document provides an explanation of the steps required to perform a Microsoft Access toFileMaker Pro Migration project using FmPro Migrator and FmPro Migrator Developer Edition. Thismigration process includes the migration of Tables/Fields, data, Relationships, Value Lists,Forms/Reports and Visual Basic code.Revision 16FmPro Migrator 9.007/22/2020[Revision Notes: Updated to use of AccessDDRExport32.accdb with 64-bit and 32-bitcompatibility, new AccessDDRExportSaveImage.exe utility, and ij15.dll updated installation.]FmPro Migrator - Access to FileMaker Migration Procedure - 5
Step 1FmPro Migrator - Access to FileMaker Migration Procedure - 6
Office 365 Compatibility ProblemMicrosoft Office 365 installs with a Click 2 Run installer, this sandboxed installation is incompatiblewith the installation of the ACEODBC.dll file required to provide support for reading or writingAccess .accdb database files by external applications via ODBC.When an error occurs while connecting to an Access .accdb database file, FmPro Migrator checksthe registry to verify whether Office 365 has been installed. This verification checks for theClickToRunStore registry value within the Office installation. Then the appropriate error messageis displayed.FmPro Migrator Office 365 Error Dialog - Importing .accdb FilesFmPro Migrator needs to make a File DSN connection to an .accdb file to read information abouttables and fields within the database file. If the process fails due to having Office 365 installed, thiserror dialog will be displayed.FmPro Migrator Office 365 Error Dialog - Exporting to .accdb FilesWhen creating a table or transferring data into an Access .accdb file this dialog will be displayed ifOffice 365 is installed.FmPro Migrator - Access to FileMaker Migration Procedure - 7
Solution: Buy Access Standalone Version or Bundled Microsoft Office Pro VersionThe only solution to this problem, according to Microsoft is to purchase a new standalone copy ofMicrosoft Access, or buy the regular Office Pro bundle which includes Access. Using MicrosoftVolume Licensing will also avoid Office 365, and will install Access onto your computer using thestandard MSI installer.You must avoid having any components of Office 365 installed on your computer when youperform the installation of the standalone version of Access. It may be necessary to get a specialtool from Microsoft in order to remove every last part of the Office 365 software (or use a 3rd partyremoval tool), then restart Windows. One free removal tool from Microsoft is:o15-ctrremove.diagcabFmPro Migrator - Access to FileMaker Migration Procedure - 8
Access 2016 Advanced Install Options - Offline InstallerBy default, Microsoft will use the ClickToRun installer. You should download the offline installer.AccessRetail.img Disk Image File DownloadedThe AccessRetail.img disk image file should be found in your downloads folder. This screenshotshows the Access 2016 disk image file.FmPro Migrator - Access to FileMaker Migration Procedure - 9
Access ODBC Driver Error - Unable to load odbcji32.dllSolution:1) Download Access Database Engine 2010 irmation.aspx?id 132552) Run the AccessDatabaseEngine.exe executable to install or repair the Access DatabaseEngine files.FmPro Migrator - Access to FileMaker Migration Procedure - 10
Step 1 - Get Info - Access to FileMaker ProFmPro Migrator uses the information within the Access mdb/accdb file to perform the conversion oftables/fields and data from Microsoft Access to FileMaker Pro. FmPro Migrator can be running onmacOS or Windows in order to perform the conversion. It is not necessary to have a copy ofAccess running on the computer which is being used to perform the conversion, but FileMaker Prois required.When using FmPro Migrator on macOS, the Actual Technologies ODBC Driver for Access isrequired.Step 1 - Click FileMaker TabLaunch FmPro Migrator, then click on the FileMaker tab at the top of the window.FmPro Migrator - Access to FileMaker Migration Procedure - 11
Step 1 - Get Info - Select Output DirectoryFmPro Migrator stores migration process information within a SQLite database file namedMigrationProcess.db3. This file contains the metadata for the source Access database file,including tables, fields, table creation SQL code and status info. Therefore the first step in themigration process is to click the Browse button to select the output folder FmPro Migrator will usewhen creating the MigrationProcess.db3 file.(1) Select the output directory, then (2) select Access from the Source Database menu.(3) Create an ODBC DSN to the FileMaker database using the name already shown in theDestination Database ODBC DSN field. Or you may create an ODBC DSN with a different nameand enter the name in this field.[Details are provided in the following pages for installing FileMaker ODBC drivers and creating theODBC DSN.]Note: FmPro Migrator will automatically create a File DSN to read table info from the Accessdatabase. But you should create an ODBC DSN (shown later) when transferring data from Accessto FileMaker.FmPro Migrator - Access to FileMaker Migration Procedure - 12
Continue Migration.Tip: To restart an existing migration project, select the output directory, then select ContinueMigration. from the File menu.Click the yellow Continue button to open the Migration Process window.Step 1 - Get Info - Drag & Drop Access FileDrag & Drop the Access file onto the Step 1 Get Info icon.Step 1 - Get Info - TroubleshootingNote: FmPro Migrator makes a file DSN connection to read the structure info from the Accessdatabase file. On macOS, this process requires the Actual ODBC Driver for Microsoft Access fromActual Technologies (www.actualtechnologies.com).On Windows, the Microsoft Access ODBC driver is pre-installed when Microsoft Access is installed.FmPro Migrator - Access to FileMaker Migration Procedure - 13
Step 1 - Get Info - Select Continue. MenuAfter the Gathering Info. dialog disappears, select the File - Continue Migration. menu or clickthe yellow Continue. button.FmPro Migrator - Access to FileMaker Migration Procedure - 14
Step 1 - FileMakerDB & Migration Process WindowsAfter Continue Migration has been selected, the Migration Process window will open. FmProMigrator will also save a FileMaker template database file named FileMakerDB.fp7/.fmp12 to theoutput directory and will open the FileMaker database file.FmPro Migrator - Access to FileMaker Migration Procedure - 15
Install FileMaker ODBC Driver - macOS (FileMaker 7,8,910)Copy SequeLink.bundle File to /Library/ODBCFor FileMaker 7 Databases on macOS:Manually copy the SequeLink.bundle file from the ODBC Client Driver folder on the FileMakerapplication CD or ESD dmg to the /Library/ODBC folder within macOS.Note: Using the FileMaker ODBC driver with FileMaker Pro/Advanced 7 requires the FileMakerdatabase file and ODBC driver to be open locally on the same computer where FmPro Migrator isrunning. The exception to this requirement is when the database file is opened with FileMakerServer Advanced.Download & Install iODBC Driver Administrator from OpenLink SoftwareDownload and install the iODBC Data Source Administrator, provided by OpenLinkSoftware,available from (www.openlinksw.com). Downloading the iODBC framework or any trial version ofan OpenLink Software ODBC driver for macOS will provide you with the iODBC Driver Manager.The iODBC driver manager does not stop working after the trial software expires. The iODBCdriver manager provides a test feature which enables you to quickly test ODBC driver connectionsafter creating or updating an ODBC DSN.FmPro Migrator - Access to FileMaker Migration Procedure - 16
Add the DriverOpen the OpenLink ODBC Administrator application, (1) click on the ODBC Drivers tab, then (2)click the Add a driver button.FmPro Migrator - Access to FileMaker Migration Procedure - 17
Specify Name and Pathname to Driver(1) Enter a descriptive name for the driver, this is a name which you will select when creating anODBC DSN which uses the driver. (2) Enter the full pathname to the ivslk component within theSequeLink.bundle file.This image shows part of the pathname to use for a FileMaker 9 ODBC driver, with the fullpathname listed s/ivslk20.dylibThe name of the ivslk component changes with each revision of the DataDirect SequeLink driverfile. You can't count on it staying the same, so it is recommended that you navigate to the locationof the SequeLink.bundle file and select Ctrl Show Package Contents to view the contents of theMacOS folder. Clicking the Browse button to the right of the Driver file name field doesn't allow theselection of individual components within bundle files. You always need to manually type in thispathname.FmPro Migrator - Access to FileMaker Migration Procedure - 18
(3) Click the Ok button, and the driver will be added to the list of available ODBC Drivers.If the driver doesn't get added, try to close, then reopen the ODBC Administrator program.Add a System DSN(1) Click the System DSN tab, then (2) click the Add button.FmPro Migrator - Access to FileMaker Migration Procedure - 19
Choose FileMaker ODBC Driver(1) Select the FileMaker 9 ODBC driver from the list, (2) click the Finish button.FmPro Migrator - Access to FileMaker Migration Procedure - 20
Enter System DSN Parameters(1) Enter the name of the DSN, this name must match the name shown within FmPro Migrator forthe FileMaker Pro database. (2) Enter the Port, (3) Host, (4) ServerDataSource and (5)ServerDataName. Each Keyword and Value needs entered manually in the Keyword and Valuefields. (6) After entering each Keyword/Value pair, click the Add button and the values will appearin the list of Keyword/Value pairs.(7) Click the Ok button to create the System DSN.Note: Setting up the ServerDataSource and ServerDataName values with "Default" values,enables multiple individual FileMaker Pro files to be used with the driver, without requiring achange to be made to the ODBC DSN parameters. However the limitation associated with thisconfiguration is that only one FileMaker Pro database file can be used at one time with the ODBCdriver. Having two database files open at the same time confuses the ODBC driver (even if a tablename is specified to the driver) causing none of the tables within any of the open files to be foundby the ODBC driver.FmPro Migrator - Access to FileMaker Migration Procedure - 21
Enable ODBC/JDBC Sharing within FileMaker ProODBC/JDBC Sharing needs to be enabled within any FileMaker Pro database file which is goingto be used with the FileMaker ODBC driver.FmPro Migrator - Access to FileMaker Migration Procedure - 22
Select Sharing Parameters(1) Turn on ODBC/JDBC Sharing, (2) for the currently open FileMaker Pro database file, (3) for AllUsers, then (4) click the Ok button.Test ODBC DSN(1) Click the System DSN which has just been created, (2) click the Test button.FmPro Migrator - Access to FileMaker Migration Procedure - 23
Enter the (1) Username, (2) Password, then (3) click the Ok button to test the ODBC DSN.If the test passes, this dialog will be displayed, showing that the ODBC Driver Manger has usedthis ODBC DSN to successfully connect to the FileMaker database.If the test fails:1) Re-verify the pathname to the svlk file within the SequeLink.bundle file.2) Verify that the FileMaker database file is open.3) Verify that ODBC sharing is enabled for the account entered in the connection test dialogprompt.4) Make sure that there aren't two different copies of FileMaker running at the same time. Botholder and current versions of FileMaker use TCP/IP Port# 2399 for ODBC connectivity. If this typeof conflict occurs, close both versions of the FileMaker application, and only open the one copyyou want to serve the database file being migrated.5) Try rebooting the computer (after clicking Ok to save changes and close this ODBC dialog).Then test the DSN again after rebooting.FmPro Migrator - Access to FileMaker Migration Procedure - 24
Install FileMaker ODBC Driver - macOS (FileMaker 11 )Download ODBC ManagerDownload and install the free ODBC Administrator for macOS from www.odbcmanager.netYou will use the ODBC Administrator to create and manage your ODBC DSNs on macOS.FmPro Migrator - Access to FileMaker Migration Procedure - 25
Install the FileMaker ODBC Driver(1) Open the xDBC folder on the FileMaker install CD (or installer image DMG file).(2) Double-click the FileMaker ODBC.mpkg installer to install the FileMaker ODBC driver. Followthe insular prompts.FmPro Migrator - Access to FileMaker Migration Procedure - 26
Add a System DSN(1) Click the System DSN tab, then (2) click the Add button.Choose the FileMaker ODBC Driver(1) Select the FileMaker ODBC driver from the list, (2) click the Ok button.FmPro Migrator - Access to FileMaker Migration Procedure - 27
FileMaker ODBC DSN Configuration - Page 1Click the Continue button.FmPro Migrator - Access to FileMaker Migration Procedure - 28
FileMaker ODBC DSN Configuration - Page 2(1) Enter a name for the FileMaker ODBC DSN. The name used here needs to be exactly the sameas the ODBC DSN Name you enter into FmPro Migrator.(2) Click the Continue button.Note: You can pick a different name than you see here, just make sure that you enter exactly thesame name into FmPro Migrator.FmPro Migrator - Access to FileMaker Migration Procedure - 29
FileMaker ODBC DSN Configuration - ODBC DSN Field in FmPro MigratorIn this screenshot, the FileMaker 11 database is the destination database, therefore the FileMakerODBC DSN name is entered in the Destination Database ODBC DSN field.If the FileMaker database was the source database, and the data was being copied to a differentdatabase server, then the FileMaker ODBC DSN would be entered into the ODBC DSN field forthe Source Database (not shown in this screenshot).FmPro Migrator - Access to FileMaker Migration Procedure - 30
FileMaker ODBC DSN Configuration - Page 3(1) Enter the hostname for the FileMaker database (default is localhost).(2) Click the Continue button.For a file which has been opened on your local desktop machine, leave the default setting oflocalhost.For a hosted file hosted by FileMaker Server Advanced, enter the IP Address or hostname of theFileMaker Server Advanced computer.FmPro Migrator - Access to FileMaker Migration Procedure - 31
FileMaker ODBC DSN Configuration - Page 4(1) For most locally hosted database files, enter the text "Default" into the Database field, instead ofselecting a database from the list. This way you can use any single database file withoutre-selecting the database name each time you open a new file.To use this feature, you must only have one FileMaker database file open at a time, or an error willoccur when attempting to read info from the database.(2) Click the Advanced Language button.FmPro Migrator - Access to FileMaker Migration Procedure - 32
FileMaker ODBC DSN Configuration - Page 5(1) Un-check the Auto-detect language settings checkbox.(2) Select UTF-8 from the Multi-byte text encoding menu.(3) Click the Ok button.FmPro Migrator - Access to FileMaker Migration Procedure - 33
FileMaker ODBC DSN Configuration - Page 4(1) Click the Continue button.FmPro Migrator - Access to FileMaker Migration Procedure - 34
FileMaker ODBC DSN Configuration - Page 5(1) Click the Test button.If the test fails, use the following steps to enable ODBC sharing for the FileMaker database.Note: Each FileMaker database needs to have ODBC sharing enabled individually.FileMaker ODBC DSN Configuration - Page 5 - ODBC DSN TestEnter the (1) Username, (2) Password, then (3) click the Ok button to test the ODBC DSN.FmPro Migrator - Access to FileMaker Migration Procedure - 35
FileMaker ODBC DSN Configuration - Page 5 - ODBC DSN Test(1) Click the Ok button.If the test passes, this dialog will be displayed, showing that the ODBC Driver Manger has usedthis ODBC DSN to successfully connect to the FileMaker database.If the test fails:1) Verify that the FileMaker database file is open.2) Verify that FileMaker ODBC sharing is enabled for the account entered in the connection testdialog prompt.4) Make sure that there aren't two different copies of FileMaker running at the same time. Botholder and current versions of FileMaker use TCP/IP Port# 2399 for ODBC connectivity. If this typeof conflict occurs, close both versions of the FileMaker application, and only open the one copyyou want to serve the database file being migrated.5) Try rebooting the computer (after clicking Ok to save changes and close this ODBC dialog).Then test the DSN again after rebooting.FmPro Migrator - Access to FileMaker Migration Procedure - 36
FileMaker ODBC DSN Configuration - Page 5(1) Click the Done button to save the new ODBC DSN.FmPro Migrator - Access to FileMaker Migration Procedure - 37
Enable ODBC/JDBC Sharing within FileMaker ProODBC/JDBC Sharing needs to be enabled within any FileMaker Pro database file which is goingto be used with the FileMaker ODBC driver.FmPro Migrator - Access to FileMaker Migration Procedure - 38
Select Sharing Parameters(1) Turn on ODBC/JDBC Sharing, (2) for the currently open FileMaker Pro database file, (3) for AllUsers, then (4) click the Ok button.FmPro Migrator - Access to FileMaker Migration Procedure - 39
Install FileMaker ODBC Driver - Windows - FileMaker 7,8,9,10Install FileMaker ODBC DriverRun the DataDirect SequeLink installer, within the xDBC/ODBC Client Driver Installer folder on theFileMaker Pro installation CD. Follow the prompts to install the FlleMaker ODBC Driver.Create ODBC DSNTo create a new System ODBC DSN, open the Control Panel Administrative Tools DataSources (ODBC) Control Panel.FmPro Migrator - Access to FileMaker Migration Procedure - 40
(1) Click the System DSN tab, then (2) click the Add button.(1) Select the DataDirect 32-BIT SequeLink driver, then (2) click the Finish button.If the DataDirect 32-BIT SequeLink driver does not appear within the list of available drivers,please refer to FileMaker Technical Support Knowledge Base record #357 for more details aboutthe driver installation process.FmPro Migrator - Access to FileMaker Migration Procedure - 41
(1) Enter the Data Source Name, (2) SequeLink Server Host, (3) SequeLink Server Port, then (4)click on the Server Data Source button.Set Data Source Default(1) Click the item named "Default", then (2) click the Ok button. Don't select the actual name of thedatabase shown in the list, or you will have to change the database name for each individualdatabase file which you want to use with this ODBC DSN. Selecting the Default item in the listinsures that you will always be able to open any FileMaker database file regardless of its name, aslong as ODBC sharing is enabled.Note: Setting up the Server Data Source value to the "Default" value, enables multiple individualFileMaker Pro files to be used with the driver, without requiring a change to be made to the ODBCDSN parameters. However the limitation associated with this configuration is that only oneFmPro Migrator - Access to FileMaker Migration Procedure - 42
FileMaker Pro database file can be used at one time with the ODBC driver. Having two databasefiles open at the same time confuses the ODBC driver (even if a table name is specified to thedriver) causing none of the tables within any of the open files to be found by the ODBC driver.Enable ODBC/JDBC Sharing within FileMaker ProODBC/JDBC Sharing needs to be enabled within any FileMaker Pro database file which is goingto be used with the FileMaker ODBC driver.FmPro Migrator - Access to FileMaker Migration Procedure - 43
Select Sharing Parameters(1) Turn on ODBC/JDBC Sharing, (2) for the currently open FileMaker Pro database file, (3) for AllUsers, then (4) click the Ok button.Test ODBC DSNClick the Test Connect button, enter the Username/Password to connect to the FileMakerdatabase file which is currently open.FmPro Migrator - Access to FileMaker Migration Procedure - 44
If the test fails:1) Verify that the FileMaker database file is open.2) Verify that ODBC sharing is enabled for the account entered into the connection test dialogprompt.3) Make sure that there aren't two different copies of FileMaker running at the same time. Botholder and current versions of FileMaker use TCP/IP Port# 2399 for ODBC connectivity. If this typeof conflict occurs, close both versions of the FileMaker application, and only open the one copyyou want to serve the database file being migrated.4) Try rebooting the computer (after clicking Ok to save changes and close this ODBC dialog).Then test the DSN again after rebooting.Click the Ok button to save changes and create the new System DSN.FmPro Migrator - Access to FileMaker Migration Procedure - 45
Install FileMaker ODBC Driver - Windows - FileMaker 11 Install the FileMaker ODBC driver from within the xDBC folder on the installation CD or CD imagefile.Create ODBC DSN - WindowsTo create a new System ODBC DSN, open the Control Panel Administrative Tools DataSources (ODBC) Control Panel.FmPro Migrator - Access to FileMaker Migration Procedure - 46
(1) Click the System DSN tab, then (2) click the Add button.Select ODBC Driver - FileMaker 11 - Windows(1) Select the FileMaker ODBC driver, then (2) click the Finish button.FmPro Migrator - Access to FileMaker Migration Procedure - 47
ODBC Driver Configuration - FileMaker 11 - Windows (1)Click Next button.Click the About button if you need to find the version number for the driver.ODBC Driver Configuration - FileMaker 11 - Windows (2)1) Enter a name for the ODBC DSN, (2) click the Next button.FmPro Migrator - Access to FileMaker Migration Procedure - 48
ODBC Driver Configuration - FileMaker 11 - Windows (3)1) If you are using a local copy of FileMaker Pro or FileMaker Pro Advanced, then use "localhost"as the host name. Otherwise use the IP address or hostname of the FileMaker Advanced Server.2) You may optionally click the "Connect to host ." button to get a list of database files.3) Click the Next button.FmPro Migrator - Access to FileMaker Migration Procedure - 49
ODBC Driver Configuration - FileMaker 11 - Windows (4)1) Enter "Default" as the database name. Or if you have multiple database files open locally or onthe server, then select the database name from the list or enter the name of the database. Usingthe Default keyword means that you can avoid changing the setup of the ODBC DSN when usingdifferent database files - but it means that only one file can be open at a time.2) Click the Advanced Language button.ODBC Driver Configuration - FileMaker 11 - Windows (5)1) Uncheck the "Auto-detect language settings" button, 2) select System (WinLatin1) for the textencoding, 3) click the Ok button.FmPro Migrator - Access to FileMaker Migration Procedure - 50
It has been found that for proper character encoding, the following configuration works well:1) Install the FileMaker database and FmPro Migrator on Windows. If using a 64-bit version ofWindows, use the ODBC Administrator - 32 bit (not the 64 bit) to create your ODBC DSN whenusing FileMaker Pro or FileMaker Pro Advanced.2) In the FileMaker ODBC driver, disable the Auto-Detect Language checkbox in the AdvancedLanguage dialog.3) Set the Multi-byte Text Encoding menu to System(WinLatin1) in the Advanced Language dialog.4) Enable the Perform Translation for Character Data checkbox on the last panel of the SQLServer ODBC DSN configuration.ODBC Driver Configuration - FileMaker 11 - Windows (6)Click the Next button.FmPro Migrator - Access to FileMaker Migration Procedure - 51
ODBC Driver Configuration - FileMaker 11 - Windows (7)Click the Test button.ODBC Driver Configuration - FileMaker 11 - Windows (8)1) Enter Username, 2) Password (if needed), 3) click the Ok button.Review the test results, make corrections as necessary until the test passes.ODBC Error Troubleshooting Steps:1) Verify that the FileMaker database file is open.2) Verify that ODBC sharing is enabled for the account entered in the connection test dialogprompt.3) Make sure that there aren't two different copies of FileMaker running at the same time. Botholder and current versions of FileMaker use TCP/IP Port# 2399 for ODBC connectivity. If this typeof conflict occurs, close both versions of the FileMaker application, and only open the one copyFmPro Migrator - Access to FileMaker Migration Procedure - 52
you want to serve the database file being migrated.4) Try rebooting the computer (after clicking Ok to save changes and close this ODBC dialog).Then test the DSN again after rebooting.ODBC Driver Configuration - FileMaker 11 - Windows (9)Click the Finish button.FmPro Migrator - Access to FileMaker Migration Procedure - 53
Step 2FmPro Migrator - Access to FileMaker Migration Procedure - 54
Step 2 - Create TablesAt this point in the process, the FileMaker ODBC driver should be installed. The Access tables canbe created in FileMaker Pro either by pasting the tables into FileMaker Pro Advanced via theClipBoard, or via the FileMaker Pro ODBC DSN created earlier.Note: Starting with FileMaker 16, both FileMaker Pro and FileMaker Pro Advanced allowcopying/pasting of tables via the clipboard - so the older ODBC method is no longer detailed inthis manual.Step 2 - Create Tables via ClipBoard - Using FileMaker Pro AdvancedIf FileMaker Pro Advanced is being used, it is faster to create the tables by pasting the Table XMLcode via the ClipBoard.This process creates all of the tables at once, without requiring each table to be clicked in the list ofFmPro Migrator - Access to FileMaker Migration Procedure - 55
tables.Click the Copy All Tables to ClipBoard button on the Tables Tab of the Migration Process window.Step 2 - Create Tables via ClipBoard - WinAutomationWhile gathering info from the Access file, FmPro Migrator created and opened a new emptyFileMaker Pro database file named FileMakerDB.fp7/.fmp12 within the output directory.FmPro Migrator will install and run a WinAutomation Robot (or AppleScript on macOS) which willautomatically open the Manage Database window, and will also click the Tables tab.Just click the Paste button to paste the tables which have already been copied to the clipboard byFmPro Migrator.Note: Starting with FileMaker 16, both FileMaker Pro and FileMaker Pro Advanced allowcopying/pasting of tables via the clipboard.FmPro Migrator - Access to FileMaker Migration Procedure - 56
Step 2 - Create Tables via ClipBoard - Define/Manage Database. Menu - ManualProcessWhile gathering info from the Access file, FmPro Migrator created and opened a new emptyFileMaker Pro database file named FileMakerDB.fp7/.fmp12 within the output directory.If the WinAutomation Robot (or AppleScript on macOS) doesn't run, you can open the ManageDatabase window manually.Select Define/Manage Database. from the File menu within FileMaker Pro Advanced.FmPro Migrator - Access to FileMaker Migration Procedure - 57
Step 2 - Create Tables via ClipBoard - Paste Tables(1) Click the Tables tab (if necessary), (2) then click on the Paste button.Note: If the Paste button is grayed out, this means that the table XML code didn't get copied to theClipBoard before the Define/Manage Database dialog was opened. If this happens, click the CopyAll Tables to ClipBoard button again from within FmPro Migrator. Switching from the Fields tab andthen switching back to the Tables tab will cause FileMaker Pro Advanced to check the ClipBoardagain for Table XML info. When the Table XML code is found on the ClipBoard, the Paste buttonwill be enabled.FmPro Migrator - Access to FileMaker Migration Procedure - 58
Step 2 - Create Tables via ClipBoard - Paste Tables ResultThe new tables will be created and then displayed within the Tables list. FileMaker Pro Advancedwill also create a basic layout and a TO on the relationship graph for each of these new tables.Click the Ok button to close the Manage Database window.FmPro Migrator - Access to FileMaker Migration Procedure - 59
Step 3FmPro Migrator - Access to FileMaker Migration Procedure - 60
Step 3 - Transfer Data - Access to FileMaker ProConfigure Access ODBC DSN NameCreate an ODBC DSN for the Access database file matching the name shown in the Table Detailswindow, and enter the name of the new ODBC DSN in the Source DSN field on the Table Detailswindow. It is not usually necessary to enter a username/password for Access database files.FmPro Migrator - Access to FileMaker Migration Procedure - 61
Access ODBC DSN
1.1 Overview 5 2 Step 1 2.1 Office 365 Compatibility Problem 7 2.2 Step 1 - Get Info - Access to FileMaker Pro 11 2.3 Install FileMaker ODBC Driver - macOS (FileMaker 7,8,910) 16 2.4 Install FileMaker ODBC Driver - macOS (FileMaker 11 ) 25 2.5 Install FileMaker ODBC
FileMaker Pro/FileMaker Pro Advanced - refers to FileMaker Pro or FileMaker Pro Advanced version 8.5 or higher. In general, the term FileMaker Pro may refer to either FileMaker Pro or FileMaker Pro Advanced, unless specifically noted otherwise. Bento - refers to Bento database versions 1.
4) Drag & Drop the FileMaker Pro 2,3,4 files onto the FileMaker Pro 6 software window. Each file will be converted to a new file having the .fp5 file extension used by FileMaker Pro 6. 5) Proceed to the next step - FileMaker Pro 5,6 File Preparation. FileMaker Pro 5,6 - File Preparation 1) Make a c
For example, if you want to convert FileMaker Pro 5.5 (.fp5) files to FileMaker Pro 13: 1) Download the FileMaker Pro 11 Trial version from the tech note provided above. 2) Convert the .fp5 files into .fp7 files using the FileMaker Pro 11 Trial version. 3) Convert the .fp7 files
FmPro Migrator - FileMaker to SQL Server - 12 (1) Click the System DSN tab, then (2) click the Add button. (1) Select the DataDirect 32-BIT SequeLink driver, then (2) click the Finish button. If the DataDirect 32-BIT SequeLink dri
This document provides an explanation of the steps required to convert FileMaker Pro layouts to HTML files using FmPro Migrator Developer Edition. Revision 01 3/19/2009 This Layout to HTML conversion procedure assumes that the database tables and data have already been converted into a SQL database.
FileMaker Pro, and then turn it back on afterwards. By default, FileMaker Pro will be installed in this folder: C:/Program Files/FileMaker/FileMaker Pro 11 for a 32bit computer, or C:/Program Files (X86)/FileMaker/FileMaker Pro 11 for a 64bit computer.
developer can be your competitor. FileMaker is also expanding into the Linux arena with the announced version of FileMaker Server 5.5 for Linux. That is nothing something that Microsoft will likely be doing. FileMaker is really a suite of products: FileMaker Pro, FileMaker Server, FileMak
The new CS-LSA is based on a number of ASTM standards at a specified revision as documented in Subpart A of CS-LSA. The structure of the ASTM standard F2245 at revision 09 is used as the basis for this CS-LSA, including the numbering system. 7. The differences between the initial issue of CS-LSA and the current ASTM standard can be summarised as follow: The scope is extended to aeroplanes with .
