If you have any ideas, please let me know so we can have a look at the issue.Thank you.Eric.
I have seen similar before. This was in a W8.1 OS using iBase v8.9.11 - it was refusing to recognise the network server when mapped to a drive letter (e.g. I:\) but would let the user in if they typed the full server-path out longhand into the Open dialogue box e.g. \\dummydrive001\iBase. I know this happened to at least 4 of our users because they made contact with me to help them get it working again.TBH I wasn't even thinking the iBase software was the issue, as our network stability at that time could be at best described as "flaky". The software had been running fine on that platform for more than 18 months, so a new network / OS user profile issue seemed more likely. The solution I discovered was to get the user to disconnect/forget the mapped server, reboot and then remap the server-path to the same letter. iBase user history then did still show the same database twice - as per your last screenshot.We're in the process of moving our users across to W10 OS on a new network infrastructure. We're still running v8.9.11 until all users have migrated and then we're going to a v9 build. So far, nobody has complained about this scenario happeningI was hoping that the recoding work undertaken for the v9 release may have finally fixed a similar login 'frustration' (it may not be a bug but a deliberate design, though not one the users like) which I first discussed with i2 staff back in late 2012/early 2013. If a user has access to more than one database, with different .ids files in different folders, iBase refuses to switch between databases unless you log in to the .ids first.To clarify, let's say I have access to Database A and Database B. They are in different folders with different .ids files.- Yesterday I used Database A. I close iBase down at the end of the day.- Today I want to use Database B. When I open iBase, it offers to open Database A for me as the Last Used. I press Cancel.- I then use Open... and navigate to the folder hosting Database B and point to the .idb file.- I will then get an error message that the security file is incorrect. Rather than looking at the .ids that is in the same folder as the .idb for Database B, iBase will continue looking at the security file for Database A, because that's the last one used. The only workaround is to run the Login process first, navigate to the Database B folder to find the .ids then run Open database.Some Developers may say that this is a more sensible way to design the security, but it is a less pleasant user experience. Not every Crime Analyst is a confident computer-user; many of my colleagues are brilliant at their role but become flummoxed by various computer error messages they receive when software doesn't work nicely. iBase is merely a tool to obtain the data they need for their real skills, and the user experience should be the key. When people find a system confusing or frustrating, they go look for alternative ways to get the same data. I hope the whole login/open process is tidied up in a future release.Ant