Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

4.11 not allowing Application to write long filenames

Status
Not open for further replies.

Denda

MIS
Oct 30, 2001
237
US
Hi all -

I have an application that writes a file lock to the server when a certain table in a database is being updated. When the application writes to the server(4.11), the server truncates the filename to 8 char, which in the long run, the application is looking for the full file lock name, doesn't see it & then doesn't lock the table.

Long name support is enabled & we don't seem to have this problem with anything else, but this application. Has anyone seen anything like this & if so, how did you get around it?

Thanks a ton!
 
HI.

I have not seen this specific problem, but have seen some other strange things.

You can try the following:

* Try mapping the drive using bindery names SERVER/VOLUME, instead of NDS names - in some cases it makes a different.
It will probably be the same but won't hurt you to try.
* Update the server software by installing SP9 for NW4.X
* Update the client with the latest client32 software. (I guess this has best chances to help you).

Bye
Yizhar Hurwitz
 
Double check the long name space by typing VOLUMES at the command consile. This will list the volumes and their name space configuration. If the volume you are saving this to lists only DOS, then type ADD NAME SPACE LONG <volume_name>.

I hope this helps.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top