>>ITEM : N01007
>>DATE: 07/30/97
>>TYPE: I
>>TITLE: Repetitive N_FUNIQUE anomaly under Novell Client32
>>PRODUCT(S):
NetLib 6.5, 6.5a, 6.5b, 6.5c for Clipper
NetLib 2.5, 2.5a, 2.5b for FoxPro
>>PLATFORM(S):
Netware using Novell Client32
>>SUMMARY:
When issuing N_FUNIQUE in a tight loop, you may accidentally end up with the same "unique" filename two times in a row. This only occurs when the files are created on a shared volume (i.e., not a local drive). This does not occur when the workstation is running a Microsoft Client.
>>MORE INFORMATION:
DOS and all clients use the current time to create a unique file name. Novell Client32 looks at both filename and extension to determine uniqueness, while DOS and MS Clients look at just the 1-8 character filename. Therefore, Client32 considers "ABCDEFGH.123" and "ABCDEFGH.456" to be unique names, while DOS and MS Clients do not. In general, most developers would consider the latter method to be the preferable one.
>>RESOLUTION/FIX:
A permanent workaround will be added to a future maintenance release. As a temporary work-around, add a 1 second delay between iterations of N_FUNIQUE.
>>EXAMPLE(S):
INKEY(1)
cFile = N_FUNIQUE(".DBF")
>>SEE ALSO:
>>COPYRIGHT 1997 Communication Horizons
All rights reserved worldwide.
No distribution without specific consent of publisher.
Knowledgebase
Top Home
