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: 

Solution: Enabling Macros on Workbooks from OneDrive

Reddit · r/excel

60+ comments · 2 years ago

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.