>Hi,
>I'm looking for information on an apparent known bug in Foxpro/Windows 2000 reported to me by a coworker who is now on vacation. He reportedly spoke with an tech a Microsoft about a problem where seek does not find a record that it should. It was supposed to be a known bug with Windows 2000, Visual Foxpro and memory cacheing but I can find nothing about it. Does anyone know about any such bug?
Here's what I found in TechNet. Does this sound like the problem you're referring to?
PSS ID Number: Q135361
Article last modified on 02-15-2000
WINDOWS:3.0,3.0b,5.0,5.0a,6.0
======================================================================
-------------------------------------------------------------------------------
The information in this article applies to:
- Microsoft Visual FoxPro for Windows, versions 3.0, 3.0b, 5.0, 5.0a, 6.0
-------------------------------------------------------------------------------
SYMPTOMS
========
When you use the SEEK command and there are trailing spaces in the seek key, the
seek fails if you previously used this command:
SET COLLATE TO "machine"
However, the seek succeeds if you previously used this command:
SET COLLATE TO "general"
WORKAROUND
==========
Remove the trailing spaces from the seek key.
Précédent
Suivant
Répondre
Voir le fil de ce thread
Voir le fil de ce thread à partir de ce message seulement
Voir tous les messages de ce thread
Voir tous les messages de ce thread à partir de ce message seulement