Rank: Administration
Groups: Administrators, Beta Testers Posts: 3,110 Location: Auburn, GA Thanks: 1009 times Was thanked: 500 time(s) in 414 post(s)
|
Hi Bart:
There is an enhancement to the .29 version that shows the path to LOG.DBF if you specify the path with DATA= on the command line or shortcut. I also added some extra error checking to make sure that a log.dbf actually exists at the specified location.
I am using the standard .Net Directory.Exists and File.Exists to make this determination. I tested it here using a different computer on my LAN, using a UNC path in DATA=, and it works fine.
So please do this. Start .27, and go to tools/advanced/path and file info. Note the location of the LOG.DBF that it is using. Make sure that it is using the one on the network drive -- the one that you think it is using. It could be that log.dbf is not actually at the location you think it is, and LOGic is finding another one somewhere along the path to use. Prior to .29, LOGic didn't actually check that there was a log.dbf at the path specified by DATA=. If it found a log file to use somewhere, it was happy.
Let me know. If that doesn't resolve it, please send me the DATA= path, a screen shot of tools/advanced/path and file info from .27, and the exact error generated by .30.
Tnx for using LOGic.
73,
Dennis WN4AZY
|