To change the database connection in EDGEBIC, open Settings and then the DataSource tab, point the current provider at the file or database you want (Browse to a different local file, or change the SQL Server Database name), click Test connection to confirm write access, then Apply and restart. EDGEBIC by User Solutions reconnects on the next launch, and because the switch only changes where data is read and written, the database you leave is untouched and stays available as a fallback.
This post covers repointing the connection within a provider, for example to a restored backup or a different file. To change providers entirely, see how to switch from SQLite to SQL Server in EDGEBIC; the full task library is at the EDGEBIC how-to hub.
Before You Start
- You know which database you want to connect to, and where it is.
- If it is a restored or copied file, confirm it is not marked read-only in Windows Explorer.
- You are ready to restart. Changing the connection always requires a restart, so save any in-progress edits first.
The Steps
- Open the DataSource tab. From the main navigation open Settings, then DataSource. The card at the top shows the active connection, its provider, and the current file path or server and database.
- Keep or set the provider. Leave the provider where it is to repoint within the same engine. Only SQLite and SQL Server are supported; PostgreSQL and MySQL appear in the list but are not available.
- Point at the new database. For SQLite, use Browse to select a different file, or type the full path. For SQL Server, change the Database name (use Refresh to list databases on the server).
- Test the connection. Click Test connection. For SQLite this confirms the file opens with write access; for SQL Server it confirms the server is reachable and sign-in succeeds. A database that does not exist yet will be created on first launch.
- Apply and restart. Click Apply and restart. If you want a safety copy of the current database first, click Export current first.
- Confirm the reconnection. EDGEBIC restarts on the new connection. If the target file came from an older version, it reconciles its internal version bookkeeping and applies any schema updates automatically.
What Changes When You Save
| Surface | Effect |
|---|---|
| Active database | EDGEBIC now reads and writes the database you pointed at. |
| The database you left | Untouched; still available if you change the connection back. |
| A restored older file | Schema updates since the backup are applied on connection; data is not altered otherwise. |
| Users and sign-in | Users live inside the database, so a different database means different accounts and possibly a new administrator prompt. |
| The application | Restarts immediately on the new connection. |
How to Check It Worked
After the restart, open Settings and then DataSource and read the connection card. It should show the file path or server and database you selected, with a green Connected chip. Then open a data screen you recognize, for example Product or Job View, and confirm the records are the ones you expected from that database. If they match, the reconnection succeeded.
Common Mistakes
Connecting to a read-only restored file. Test connection can pass on a read-only file, then the first save fails with a confusing disk error. Clear the read-only attribute in Windows Explorer before you reconnect.
Pointing two running copies at one file. A single-file database is not built for concurrent access. Never open the same local file from two running copies of EDGEBIC. For shared access, use a SQL Server database.
Expecting different accounts to travel. Users live inside each database. Connecting to a different database means different users and possibly a fresh administrator prompt; that is normal, not an error.
Skipping the backup. Before repointing a production connection, click Export current first. It costs one click and gives you a clean return path.
What to Do Next
If your goal is to move to a shared, multi-user setup rather than just repoint a file, how to switch from SQLite to SQL Server in EDGEBIC is the full changeover, and EDGEBIC deployment options explained frames the local-versus-shared decision. To make restore-ready backups a habit, see how to back up the EDGEBIC database, and to carry a single-user setup to another PC, how to move EDGEBIC to a new computer. The EDGEBIC product page shows where the database sits in the platform.
Expert Q&A: Deep Dive
Q: I restored a backup file, pointed EDGEBIC at it, and the connection tests fine, but the first save crashes. What happened?
A: The restored file is almost certainly marked read-only. Backup tools frequently set the read-only attribute on the files they write, and EDGEBIC can open a read-only database for reading, so Test connection passes, but the first time it tries to write it fails with a confusing disk error. Close EDGEBIC, clear the read-only attribute on the file in Windows Explorer, and reconnect. The SQLite check does warn about a read-only file when it can, but clearing the attribute up front avoids the whole problem when you are restoring backups.
Q: We keep the shared database on a network share. Can EDGEBIC connect to a file there?
A: It can, but read the trade-offs. Pointing the connection at a file on a network path is supported, and the file must be writable by the Windows account running EDGEBIC. Performance can degrade on a high-latency share, and, most important, you must never point two running copies of EDGEBIC at the same local database file, because a single-file database is not meant to be opened concurrently that way. If several planners need the same live plan, use a shared SQL Server database instead of a shared file; that is exactly what the SQL Server provider is for.
Frequently Asked Questions
Ready to Transform Your Production Scheduling?
User Solutions has been helping manufacturers optimize their production schedules for over 35 years. One-time license, 5-day implementation.
User Solutions Team
Manufacturing Software Experts
User Solutions has been developing production planning and scheduling software for manufacturers since 1991. Our team combines 35+ years of manufacturing software expertise with deep industry knowledge to help factories optimize their operations.
Share this article
Related Articles
How to Create a Watched-File Integration in EDGEBIC
Create a watched-file integration in EDGEBIC: point it at the file your ERP drops, pick the target entity and import mask, set the debounce, and let a new file trigger the run.
How to Rehearse an Integration With the EDGEBIC Simulator
Use the built-in Simulator to provision demo data, watch real integration runs happen, and prove the mechanism before you point anything at a live ERP. Includes the tear-down rule.
How to Run an Integration Now and Pause All Schedules in EDGEBIC
Force one integration to run with Run Now, cancel a run in progress, disable a single definition, or tick Pause all schedules to stop every automatic sync for the session.