Chip-Scale ICs: Pick and Place Risks

Chip-Scale ICs: Pick and Place Risks - Gemini AI Chat

PCB Silkscreen - Stroke Fonts are Preferred

PCB Silkscreen Text Font Preferences - Gemini AI Chat

PCB Silkscreen Registration Accuracy

PCB Silkscreen Registration Accuracy  - Gemini AI Chat

Open PDF files in the Acrobat Reader Desktop App

 Open PDFs in Acrobat Reader from Chrome

Git repo - Hard Reset using TortoiseGit

Important Tip: 

Create a Backup Copy (zip file) of your local repo on your machine then . . .

To perform a hard reset on a Git repository using TortoiseGit, you'll use the "Reset" option from the context menu. 

This action discards all uncommitted changes in your working directory and aligns your branch's state with a specific commit. 

Because a hard reset is a destructive action, it's crucial to be certain you want to permanently discard your changes before proceeding. ⚠️

---

Step-by-Step Guide

1. Right-Click on your Git-controlled folder to bring up the context menu.

2. Navigate to TortoiseGit > Show log.This will open the reset dialog box.

3. Select a Commit in the Repo, then Right Click on Reset "master" to this. . .  

4. In the dialog box, you have two main options to configure the reset:

• "To commit": This field allows you to specify the target commit to which you want to reset your branch. You can either type the commit hash, branch name, or a tag name directly into the box. Alternatively, you can use the ... button to open the log dialog and select the desired commit visually.

• "Reset type": From the Dialog Options select "Hard Reset . . .". This is the key step. Choosing "Hard" will discard all your local changes (staged and unstaged) and move your branch's pointer to the selected commit. 

• The other options, "Soft" and "Mixed," are less destructive and won't be covered here.

• 

• 
  

5. Once you've selected the correct commit and chosen "Hard" as the reset type, click "OK"..

After clicking "Yes," TortoiseGit will execute the hard reset, and your working directory will be reverted to the state of the selected commit. 

All files that were changed or added since that commit will be permanently deleted from your local copy. 

Git Repo Alerts

The latest release (10-Aug-2025) or later of the Parts Frontend application (Parts_Frontend.accde) includes Git Repo Status Alerts.

The purpose of the Git Alerts are two fold. 

1. To remind and prompt users to commit changes staged in their local repositories to the master repository.
   
   
2. To remind and prompt users to Pull Changes from the master repository when their local repo is not in sync with the master repository.

The option to use Git Alerts can be enabled or disabled in the Parts Frontend Config Table or by closing Parts and editing the user.ini file. The user.ini can be found in the same folder as the Parts Frontend.accde file.

If you concerns or questions please Contact Parts

That's it !

Ai Chats for Parts

Updated July 22, 2025

Video Link  https://youtu.be/XAOUxPQ_sR8

Parts Chats with Microsoft Copilot or Google Gemini.

To enable the Ai Chats an AI Chat Request Template is required.

See Parts > Configuration > Ai Chat Ask Template.

Example Templates for Ai Chat Requests:

Gemini Search DigiKey, Mouser and Octopart for Part Number, include RoHS status, stock and price ranking. Provide URL links for Part Number Alternate Parts,

Copilot Search DigiKey and Mouser for Part Number, include URL links, Alternate Part URLs, RoHS status, stock and price ranking. Include a Link for Octopart. Please begin the Conversation Name with Part Number.

Tips:

Copy and Paste one the above Chat Requests or Create your own.

To start a Chat Select a Part Number or Description in Parts then Click on | Ai Chat |

Single click left mouse button on one of the | Ai Chat | labels (URL Link) and wait for Chat to complete before starting a another Chat request. 

Best practices . . . Close the Chat window before starting another Chat.

Selecting by Description may be your best choice for finding Alternate Parts

Requirements:

The Chat must begin with Copilot or Gemini and contain the keyword Part Number.

The Part Number in the Template will be replaced with the selected Part Number or Description. 

The Chat Ask Template is limited to 255 characters.

Contact Parts if have any questions about Parts and Ai Chats.

That's It !

Share Access Databases on Cloud Drives - Don't Do it !

Here's a breakdown of why sharing an Access database directly on OneDrive, Dropbox, Google Drive is problematic and what alternatives to consider:

Why it's not recommended:

• Synchronization Issues:

  OneDrive synchronizes files by downloading and uploading the entire file. When multiple users are working on the same Access database, this can lead to conflicts and overwrites as each user's changes are synced.
• Performance Degradation:

  Opening and saving the entire database file repeatedly can cause significant performance issues, especially with larger databases.
• Potential for Data Corruption:

  The frequent syncing and potential conflicts can lead to data corruption and loss. 

Recommendations:

1. 1. Split the Database:

   • Divide the Access database into a front-end (containing user interface elements like forms, reports, and queries) and a back-end (containing the data tables). 
   • Place the back-end on a shared network location (like a shared folder on a server or a NAS drive). 
   • Each user can then have a copy of the front-end on their local machine. 
   • This allows multiple users to work with the database concurrently without directly interfering with each other's changes.
2. 2. Consider Cloud-Based Database Services:
3. • Cloud hosted MySQL database solutions offer scalable and reliable alternatives. 
   • These services are designed to handle concurrent access and data management efficiently. 
   • They can be more complex to set up initially but offer long-term benefits for larger or more complex databases.In summary, while OneDrive can be convenient for sharing various file types, it's not the right tool for sharing Access databases due to synchronization and performance limitations. Splitting the database and using a cloud-based database solution is a better option for multi-user database sharing.

Parts is a split Access Database with a front-end application that supports both Local Access databases and remote cloud hosted MySQL databases.

Contact Parts for an online demo or to discuss how to create a shared Altium database library.

Randy Clemmons

How to Enable Excel Macros for *.xlsm Files on OneDrive

This post is being made in the hopes that it will save some other people time that are still looking for a fix, or will be looking for a fix in the future.

1. Open Excel

2. Navigate to Trust Center Settings

   1. Developer > Macro Security OR

   2. File > Options > Trust Center > Trust Center Settings

3. Go to Trusted Locations

4. Click "add new location" and put https://d.docs.live.net in the text box that pops up.

   1. Be sure to click the checkbox "Subfolders of this location are also trusted"

5. Click Ok and restart excel.

Note, this will trust all macros of all files in your OneDrive, so I recommend taking the appropriate security steps to ensure you're only saving files in OneDrive (that you want to open in app, at least) that you trust.

Source: 

Enabling Macros on Workbooks from OneDrive - reddit

That's it !

Git or SVN ?

Git is overwhelmingly more popular than SVN (Subversion) in the current landscape of version control systems.

Here's a summary of the popularity comparison:

• Dominant Leader: Git has been the undisputed leader for over a decade. Recent surveys, like the Stack Overflow Developer Survey, consistently show Git adoption rates well over 90%. For example, in 2025, Git's usage is estimated to be around 93.87%.
  
  
  
• SVN's Decline: SVN, while once widely used (it was the dominant system before Git), has seen a significant decline in popularity. Its usage is now typically in the low single digits, around 5% according to recent data.
  
  
  
• Reasons for Git's Popularity:
  • Distributed Nature: Git is a Distributed Version Control System (DVCS), meaning every developer has a full copy of the repository. This allows for offline work, faster commits, and a more robust system with no single point of failure.
    
    
    
  • Branching and Merging: Git's branching and merging capabilities are highly efficient and flexible, making it ideal for collaborative development, especially in open-source projects and agile environments.
    
    
    
  • Ecosystem: Git has a massive ecosystem of tools, hosting services (GitHub, GitLab, Bitbucket), and a vibrant community.
    
    
    
  • DevOps and Agile: Git's features align well with modern development practices like DevOps and agile methodologies.
    
    
    
• Where SVN Still Sees Use:
  • Legacy Projects: Many older enterprise projects that built their infrastructure around SVN continue to use it.
    
    
    
  • Specific Use Cases: SVN can sometimes be preferred for projects that require fine-grained access control down to the file or directory level, or in situations where handling large binary files with strict file locking is a priority (though Git LFS helps address this in Git).
    
    
    
  • Simplicity for Beginners: Some argue that SVN has a simpler learning curve for absolute beginners due to its centralized and more straightforward approach.

In essence, while SVN still exists and is used in some niche or legacy contexts, Git has become the de facto standard for new software development projects globally.

End User License Agreement - EULA

Please refer to the EULA  which is in the download zip file Parts_x64.

Please appreciate that there are NO annual subscription fees for using Parts.

The sales of named User Keys is the only source of revenue that supports the development work of Parts.

For pricing see: Parts: Parts Application Keys

Thank you for your support,

Randy Clemmons

How to turn off Chimes in Microsoft Access

Ready to get rid of those annoying chimes . . . 

Open your Access database.

Go to File > Options. This will open the Access Options dialog box.

In the Access Options dialog box, click on the "Client Settings" tab. You'll find this on the left-hand side of the window.

Scroll down to the "General" section.
Look for the setting labeled "Provide feedback with sound."

Uncheck the box next to "Provide feedback with sound." This will disable most of the built-in sound effects in Access.

Click "OK" to save your changes.

Here's what actually worked for me . . .

Control Panel > Hardware and Sound > 

Change system sounds > Windows > Exclamation > None