Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Odd Issues following NetWare Upgrade 3.2 to 5.1
Message
General information
Forum:
Visual FoxPro
Category:
Troubleshooting
Miscellaneous
Thread ID:
00393406
Message ID:
00393918
Views:
15
The only other thing I can think of is an access right accidently getting set on the FPT file.

I have a few customers using NW 5 with VFP 6 that have tables with memo fields, but they are not experiencing problems writing data back to the memo fields.

>We are not running the Client 32 as it interfers with our NT scripts (Kixstart 32). Thus, we are still using the MS Client for NetWare with bindery connections. Also, I am running Max Rec Locks at 2400 as required by Peachtree Acct software.
>
>So, do you have any suggestions for the Max File Locks on NetWare 5.1? I had seen something about the Extended File Handles, but of course that it is moot without the Client 32.
>
>Thanks for the response. Look forward to any further ideas you may have given the above.
>
>Regards,
>
>Jack Mendenhall
>
>-- Will Never Buy another Novell Product Again --
>
>>>We just migrated our primary production server from Novell NetWare 3.2 to 5.1 w/latest patches. We now have a problem with users working with memo fields.
>>>
>>>The routine can programmatically add to the memo field a timestamp along with the user ID, but the user gets File Access Denied when attempting to add data to the memo field. The problem comes up in both FoxPro for DOS and VFP 5/6. No changes in code, only NOS...
>>>
>>>TIA...
>>
>>Have you also upgraded the clients to the current version of Client32? Also, in the Network Neighborhood properties of of the Netware Client, Advanced Settings, set the USE EXTENDED FILE HANDLES to ON. On the server, make sure your MAXIMUM RECORD LOCKS PER CONNECTION and MAXIMUM FILE LOCKS PER CONNECTION are high enough.
>>
>>Do you use NetLib with VFP? If so, some of their functions fail with NW 5.
Mark McCasland
Midlothian, TX USA
Previous
Reply
Map
View

Click here to load this message in the networking platform