|Home » Technical Support » DBISAM Technical Support » Support Forums » DBISAM General » View Thread|
|Messages 1 to 3 of 3 total|
|Remote Access on Windows 7.|
|Mon, Mar 29 2010 12:20 PM||Permanent Link|
I have a business remote from me trying to set up DBISAM Server.
1. DBSRVR is running & shows the correct ports.
2. DBSys can open the tables via a remote connection.
3. DBAdmin can log-in and edit User Settings required by the App.
When I fire up the App it falls over instantly. The first attempt to call "Connect" on the DBISAMDatabase Component fails.
The bizarre thing is I don't get any of a series of my own error messages (i.e. failure to create Session, failure to find Users table for Log-in etc., etc.) the error message they receive is just "table or back up file not found", which I think is one of DBISAM's "own" error messages, which normally gets triggered if there is something wrong with the DBSRVR ... but I can clearly see that is OK.
... sorry for such an annoying, vague post!
|Mon, Mar 29 2010 12:25 PM||Permanent Link|
Sorry, one more piece of information:
I hold the connection settings in the Registry, and my app makes a call to the registry to find these settings. It does this right at start up.
Is it possible that Windows 7 is stopping my App from accessing the registry?
... unfortunately I don't even have a copy of Windows 7 myself on which to test all this! I think I may have to buy one, curses.
|Mon, Mar 29 2010 12:48 PM||Permanent Link|
I have figured it out.
Win 7 security policies meant that my PRIVATE DB (for temp files) was illegal for the users.
I have moved this to an accessible, shared folder & the system works fine again ... sorry, but a useful gotcha to know. (