>>>Has anybody beat this problem before?
>>>After a system crash we ran FIXFOXPO on some files that were messed up. Now, everyone that trys to log into SBT gets an INVALID USER message.
>>>I have turned SYUUSER.DBF every which way but loose. deleted, recreated the index. everything looks good. Read the manual, studied the code, left a message at SBT.com
>>>Last resort will be a restore from a tape backup.
>>>Has anyone heard of this problem?
>>>
>>>Ed
>>
>>Hi, I've not had this error before and we use FoxFix. Can you log in at all? What version of SBT (VisionPoint, Pro)?
>
>We're using version 3.0i. We finally got up and running by restoring syuuser.* from a tape backup. I think the problem was caused when we tried to fix the files using fixfoxpo and reindexing with fox 2.6. SBT uses a function in the index of the dbf file...something like: g_hidstr(userid,0)...it is some kind of encryption deal that probably blew up when I tried to reindex it from 2.6.
>Can Foxfix repair sbt stuff outside of SBT?
>Before we restored from tape, no one could get in as system administrator or anything.
>
>SBT responded to my call for help about 14 hours later with a request for my support contract number.....hmmmmmm.

Ed,
Except for encrypted password files, I think you can use FoxFix on any SBT tables...as they are just Foxpro tables. We have had several clients encounter the dreaded "Not a table/dbf" error after a hardware crash. We have had excellent results with FoxFix. We also incoporate it in most all of our custom applications. Before using a table, we test it with FoxFix, then open and/or repair and open the file. Several of our apps are notebook based programs where batteries run down while the files are open.

Don't you just love being asked for a credit card before you can get support? SBT's tech support is good.

Hope this helped.