Strange, I checked today and all is fine. But the problem persisted yesterday even after a reboot. Even on drives that were not even mapped!


>Does a similar table exist at the other locations?
>Are the other drives in your search path?
>
>
>>Hi....it's actually a free table with no app at the moment, just using the command prompt. It just seems to be this table only that this is happening to.
>>
>>
>>
>>>Hi Timothy,
>>>
>>>>The L:pertab is the real deal and no matter which drive letter I use, when I do ?dbf() it always returns "L:pertab"
>>>>strange behavior?
>>>
>>>This would happen if the table is embedded into your application and your application is launched from drive L: