开云体育

Mike,
We ran into a similar problem at Our FD site but we found the problem
early,........OP error on my pc I forgot to change the time from the default
value to our local time. I noticed the problem early and was able to easily
make the correction. we did have one other problem that might be of some
interested the groups networking the FD log.
Setup:
Server - Windows 2k Pro (wired)
Clients- 2 Windows XP Pro (wirless)

Somewhere around 200 contacts, one of the laptops lost network connectivity.
In the process of trying to fix the problem, the laptop was rebooted several
times and your program was never able to find the .mdb file again (using the
laptop) despite the fact that all the clients had the correct path and had
access/permissions to the file.

We reloaded the laptop and got the same results, unable to find the file,
despite the fact we could see it on the network.

We brought in a brand new laptop that was part of the original test setup
done the previous week, that consisted of all the above equipment plus one
extra laptop. Same problem.

We loaded up the program on a new wired XP desktop and it was unable to find
the file, either. At all times we could browse to the file and see it on
the network. Everyone had full administrative rights.

The second laptop and the file server never lost connectivity or were shut
down during the contest and there were no problems. Upon completing the
contest, we decided to run a few tests. We systematically reboot the
remaining computer and were then unable to locate the .mdb file through the
log program. Even the server could no longer see the .mdb file through the
log program.

We then started a "new contest" and found that all computers access the new
log file even after shutting down and rebooting, adding new computers, etc.
We only logged about 38 contacts in the new test contest and had no
problems.

What had happened was that when the Laptop lost the network it must have
corrupted the log.mdb file on the server.
The fix was easy to retrospect We ended up sending the file to Scott and he
had it diagnosed and fixed in less than a hour and back to us. FAST
SUPPORT!
I guess what I'm saying in a network environment make sure you have a good
network. Our whole problem was caused by one laptop in a poor wireless area.
next year we'll know better.
Outside of the above problems we found the program one of the best logging
program we've tried, easy to use even for non computer users, very
instinctive to use.
Larry KD6VUM