Hey Guys,
FYI, we were still getting this message, all be it not as often, but I think I might have remedied the issue. We keep our smg file on a network drive and were accessing it via a mapped network drive. We were running into some issues with another database file we were accessing the same way and I can across a thread on a forum suggesting that accessing database files via mapped network drives can sometimes be unstable. I changed it so we were using the full network drive to the file (ie //192.168.1.1/myfolder/myfile.smg) and the issue seems to have disappeared.
Just thought I would share that update in case someone else was running into the same issue.
Joshua
FYI, we were still getting this message, all be it not as often, but I think I might have remedied the issue. We keep our smg file on a network drive and were accessing it via a mapped network drive. We were running into some issues with another database file we were accessing the same way and I can across a thread on a forum suggesting that accessing database files via mapped network drives can sometimes be unstable. I changed it so we were using the full network drive to the file (ie //192.168.1.1/myfolder/myfile.smg) and the issue seems to have disappeared.
Just thought I would share that update in case someone else was running into the same issue.
Joshua