On 2019-12-17 15:36, David Wurdeman [email protected] [firebird-support] wrote: > Thank you for the reply > > We use an application called Ascent, which is used to analyze > vibration data from industrial machines. It stores its data in .fdb > files. These files can either be on the local machine, or on a > network share. > > The application requires Firebird to be installed and running on both > the client computer (which also runs Firebird client), and the server > with the shared .fdb databases. Firebird is fully integrated with the > Ascent program.. The only reason for the shared directory on the > server, is to have a central repository for the .fdb files (as in an > office environment).
This is simply not how Firebird databases should be handled. Sharing a database on a network drive can result in multiple clients modifying the database simultaneous with insufficient or incorrect locking, which can result in data loss or corruption. > When using the program to access a database on the server, it includes > a connection utility as per below: > > > [cid:[email protected]] Screenshots are not included on this list. > Just wanted to clarify that it’s not just a simple “accessing .fdb > files via a network share”. The Ascent program is designed natively > to work with Firebird. I think the fact that you need to share databases through a network drive is an indication it wasn't designed properly (or there is a lot more going on behind the scenes inside that application). The correct way to access a Firebird database on a network is through Firebird server. > Again—I’m not a Firebird expert. But did want to give some idea of > what we (and the application) are using it for. > > We were using this program with shared databases on a Windows 7 > computer for years with no problems. The problems started happening > when we upgraded to Windows 10. > > The Ascent program we are using is an older program, and rather > specialized.. The support for it is dwindling. I talked to their > support people, and they don’t seem too knowledgeable about Firebird. > That’s why I sought-out a Firebird support group, in hopes of maybe > getting some advice. Unfortunately, this behaviour is not part of Firebird itself, and therefor is probably a result of what your application does. The fact it works properly on Windows 7 and now has problems on Windows 10 may be a result of changes to network drive support between those versions. However, without intimate knowledge of the application, that is just guesswork. Mark
