I haven't been shocked by something in VFP in about a decade! Anyway, even though it's not pretty, I'm going to keep track of the length of each replacement and when it gets to a certain threshhold, do my simple "select in the same table". That will do it, but it really isn't pretty code. We'll put it in the dev schedule to change references to that field in our code to point to a Memo Memory variable, however, there is a big issue with clients who have created custom bits of code referencing Table.Field. If they were simple retrieval of values SCATTER NAME would work, but sometimes there is manipulation in these custom bits of code that we have no access to :(
Précédent
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