Tuesday, September 22, 2026

Migrating the MS Access "Parts" Database to MySQL

This procedure details how to generate MySQL schema and table scripts, configure server settings in MySQL Workbench, export data using pipe-delimited text files, configure the Parts Frontend connection string, and Load Data via high-speed bulk loading.

Step 1: Generate MySQL Table Creation Scripts

  1. In the Parts Frontend, open the Tools menu.
  2. Click MySQL Scripts.
  3. Select your target output folder and click OK.
  4. The utility scans the Access backend tables and outputs individual MySQL 8.0 DDL script files (`.sql`) for each table:
    • MySQL table script for mfr_links.sql
    • MySQL table script for parts.sql
    • MySQL table script for supplier_links.sql

Step 2: Execute Scripts & Enable Local Infile in MySQL Workbench

  1. Open MySQL Workbench and log into your MySQL Database.
  2. Select File > Open SQL Script from the main toolbar and browse to open each generated `.sql` file (`mfr_links.sql`, `parts.sql`, `supplier_links.sql`).
  3. Click the lightning bolt icon⚡ for each script to create schemas and tables in MySQL. Refresh the Schemas in the Navigator Panel to display the Schemas and Tables.
  4. Verify and enable LOAD DATA from local CSV files in the MySQL Workbench:
    • Run the following query to check the current setting:
      SHOW VARIABLES LIKE "local_infile";
    • If the value returns OFF, execute:
      SET GLOBAL local_infile = 1;

Step 3: Export Data to Pipe-Delimited CSV Files

  1. In the Parts Frontend Select Tools, then click Export CSV.
  2. Select the export to folder when prompted.
  3. Parts Exports each Table to a pipe-delimited (`|`), quote-qualified (`"`) text file.

Step 4: Configure Access Frontend MySQL Connection String

  1. In the Parts Frontend, navigate to Configuration.
  2. In the Select a Parts Database, i.e. Access *.accdb file. Or enter a MySQL ODBC Connection String input field, enter your DSN-less MySQL ODBC connection string:
  3. Example for AWS:
    ODBC;DRIVER={MySQL ODBC 8.4 UNICODE Driver};SERVER=parts-db-instance.c123456789.us-west-2.rds.amazonaws.com;PORT=3306;DATABASE=parts;USER=username;PWD=YourPassword;OPTION=3;
  4. Example for Localhost:
    DRIVER={MySQL ODBC 8.4 UNICODE Driver};SERVER=localhost;OPTION=3;PORT=3306;DATABASE=parts;USER=librarian;PWD=Password1;PERSIST SECURITY INFO=True;
  5. Click Apply Configuration to link the Parts Frontend to the MySQL Backend Database.

Step 5: Execute Bulk Data Import into MySQL

  1. In the Parts Frontend select Tools, then click MySQL Load Data.
  2. Close Parts Tools dialog and select Show All in the Parts Frontend to View the Records.
Contact Parts for Technical Support or an Online Demonstration.

Connecting Altium and MS Office to MySQL on AWS

This workflow outlines how to set up a 64-bit MySQL environment on AWS RDS for direct access by remote 64-bit client applications, including Altium and Microsoft Access or Excel.


Step 1: 64-Bit MySQL ODBC Driver Setup

System Requirements & Prerequisites

  • Operating System: 64-bit Windows (10/11 or Windows Server).
  • Application Bitness: Both MS Access (Office) and Altium Designer must be 64-bit installations.
  • Core Dependency: Microsoft Visual C++ 2015–2022 Redistributable (x64) (vc_redist.x64.exe). Must be Installed !

Installation & Verification Workflow

  1. Install VC++ Redistributable: Confirm Microsoft Visual C++ 2015–2022 Redistributable (x64) is installed under Windows Settings > Apps > Installed apps.
  2. Download Driver: Download the 64-bit MSI package (e.g., mysql-connector-odbc-8.4.x-winx64.msi) from the official MySQL download page under Windows (x86, 64-bit).  Recommended ODBC Drivers are versions 8.0.33 thru 8.4.which fully support caching_sha2_password .
  3. Run Setup: Select Typical or Complete installation to install the MySQL ODBC Driver.
  4. Verify Driver Registration: Press Win + S, search for ODBC Data Sources (64-bit), select the Drivers tab, and confirm MySQL ODBC 8.4 UNICODE Driver is listed.

Step 2: AWS RDS MySQL Database Provisioning

Configuration Settings

  • Engine: MySQL 8.0.14+ on AWS RDS.
  • DB Instance Identifier: parts-db-instance
  • Master Username: username
  • Public Access: Yes (enables remote client connectivity without a VPN).
  • Security Group Rule: Inbound TCP rule on Port 3306 set to Source 0.0.0.0/0 (Anywhere-IPv4).

Verification

Run the following command in Windows PowerShell to verify port connectivity:

Test-NetConnection -ComputerName parts-db-instance.c123456789.us-west-2.rds.amazonaws.com -Port 3306

No EC2 Instance is Required 

AWS RDS is a fully managed, standalone database service. Because you set Public access to Yes and added an inbound security group rule on port 3306 for 0.0.0.0/0, your remote applications (MS Access, Altium Designer, and MySQL Workbench) connect directly to the RDS endpoint over the public internet.

You only need an EC2 instance if you choose to place the RDS database in a private subnet and route traffic through an SSH jump box / bastion host rather than exposing port 3306 directly. Since you are using direct DSN-less connections over SSL with a complex password, no EC2 server is necessary.


Step 3: MySQL Workbench Installation & AWS Handshake

Installation

  1. Download the MySQL Workbench (64-Bit) MSI installer for Windows.
  2. Execute setup and complete the installation wizard.

Connecting to AWS RDS

  1. Open MySQL Workbench and click the + icon to add a new connection.
  2. Set Connection Method to Standard (TCP/IP).
  3. Set Hostname to your AWS RDS Endpoint URL and Port to 3306.
  4. Enter your Username and click Store in Vault... to enter your password.
  5. Under the SSL tab, set Use SSL to If available or Require (leave CA file paths blank).
  6. Click Test Connection and save.

To verify the active session encryption status, run this query in Workbench:

SHOW STATUS LIKE 'Ssl_cipher';

Standard DSN-Less Connection String

Use this single DSN-less connection string format for 64-bit Parts Frontend and Altium Designer (.DbLib):

DRIVER={MySQL ODBC 8.4 UNICODE Driver};SERVER=your-db.c123456789.us-west-2.rds.amazonaws.com;PORT=3306;DATABASE=parts;USER=username;PWD=Your#Complex_P@ssw0rd!2026;OPTION=3;PERSIST SECURITY INFO=True;
Contact Parts for Technical Support or an Online Demonstration.

Saturday, August 29, 2026

How to Create a SSH Key for BitBucket

Step 1: Generate an SSH Key

  • Open PowerShell or your command prompt.

  • Run the following command to generate a new SSH key pair: ssh-keygen -t rsa -b 4096

  • Press Enter through the default prompts to save the key to your user profile directory.

  • Run this command to copy your new public key directly to your clipboard: Get-Content ~/.ssh/id_rsa.pub | Set-Clipboard

Step 2: Add the Key to Bitbucket

  • Log in to Bitbucket and navigate directly to your account SSH keys settings page at https://bitbucket.org/account/settings/ssh-keys/.

  • Click Add key and paste the public key into the key field using one of the following methods:

    • Option A (Clipboard): Paste the key from your clipboard using right-click -> Paste or Ctrl + V.

    • Option B (Manual Copy): If needed, navigate to your user profile folder (typically C:\Users\YourUsername\.ssh\), open the id_rsa.pub file in a text editor, and manually copy the entire text content.

  • Type a label like SSH_BitBucket in the label field, and click Add key.

Step 3: Update Your Local Repository Remote URL and Pull

  • Open a terminal inside your local repo folder.

  • Run the following command to update your repository remote to the SSH format: git remote set-url origin git@bitbucket.org:xxxxx-llc/lib_altium.git

  • Run the following command to test the connection and pull: git pull

  • Type yes if prompted to accept the host fingerprint, and your repository will sync securely.

Step 4: Configure TortoiseGit (If Applicable)

  • If you use TortoiseGit for graphical operations, update it to use the native Windows OpenSSH client instead of PuTTY:

    • Right-click your repository folder and select TortoiseGit -> Settings.

    • Navigate to the Network section on the left sidebar.

    • Locate the SSH client path field and browse to: C:\Windows\System32\OpenSSH\ssh.exe

    • Click Apply and OK to save your changes.