>>ITEM : N00066
>>DATE: 06/25/96
>>TYPE: Information
>>TITLE: N_B_* functions and numeric Object names
>>PRODUCT(S):
NetLib (all versions) for Clipper
NetLib (all versions) for FoxPro DOS
NetLib (all versions) for FoxPro Windows
>>PLATFORMS(S):
NetWare (all versions).
>>SUMMARY:
Bindery Object names that begin with a numeric digit (0-9)
conflict with Bindery User ID numbers.
>>MORE INFORMATION:
Most of the NetLib N_B_* functions (N_B_PRWRITE, N_B_PRREAD, etc)
accept an Object as either an Object name or as a Bindery User
ID. If the string starts with a numeric character (0-9), NetLib
interprets it as a hexadecimal Bindery User ID. If the string
starts with a non-numeric character, then NetLib interprets it as
an Object name.
The problem arises when a Bindery Object name begins with a
numeric digit (e.g., "01SALES").
>>RESOLUTION/FIX:
To force NetLib to treat a numeric-prefixed string as a Bindery
Object name, rather than a hexadecimal number, prefix it with a
forward or backward slash '/' or '\'. (Note that these
characters are not valid in Object names.)
>>EXAMPLE(S):
* Prefix Bindery name "01SALES" with '/' or '\'
* Force it to be used as a Bindery name
rather than User ID:
cFullName = N_B_PRREAD("/01SALES",1,"IDENTIFICATION")
>>TIP:
Even if the first character of the name is non-numeric, you can
still prefix all Bindery names with '/' or '\'. This will save
you from having to make special code that tests for numeric-
prefixed names. For Example:
cFullname = N_B_PRREAD("/SUPERVISOR",1,"IDENTIFICATION")
This simply tells NetLib to treat SUPERVISOR as an Object name,
which it already will.
>>SEE ALSO: N00069
>>COPYRIGHT 1997 Communication Horizons
All rights reserved worldwide.
No distribution without specific consent of publisher.
Knowledgebase
Top Home
