FoxPro 2.0 Lan

FoxPro 2.0 Lan

Post by Cjwon » Fri, 06 Aug 1999 04:00:00



Help.

I am trying to run FoxPro 2.0 on a Novell 3.12 server and I am upgrading
workstaions to Windows 95. I can get foxpro to run but I am having a problem
with file locking. I can use a file once and when I go to access it again, it
says that is in use by another person. Data & EXE on the server.

Help. If I can't solve this one there may be an opening for an Analyst in
Buffalo!!!

Chuck

 
 
 

FoxPro 2.0 Lan

Post by Raj » Fri, 06 Aug 1999 04:00:00


Chuck:

Flag all the data, index, mem files etc. SRW
FLAG *.DBF SRW
FLAG *.CDX SRW
FLAG *.FPT SRW

Flag the EXE FXP APP files etc SRO

SET EXCLUSIVE OFF very early in your code so that more than one user can
use files. Check out SET REPROCESS as to how record locking is handled.

Make sure each user has a copy of their own resource file in their own
home directory or on their local machine, FOXUSER or what ever you have
set up.

That should do it. Good luck

Raj
Remove UNDERWEAR if replying directly



> >Help.

> >I am trying to run FoxPro 2.0 on a Novell 3.12 server and I am upgrading
> >workstaions to Windows 95. I can get foxpro to run but I am having a
> problem
> >with file locking. I can use a file once and when I go to access it again,
> it
> >says that is in use by another person. Data & EXE on the server.

> >Help. If I can't solve this one there may be an opening for an Analyst in
> >Buffalo!!!

> >Chuck


 
 
 

FoxPro 2.0 Lan

Post by NG » Sat, 07 Aug 1999 04:00:00


Hi Chuck
Iam presuming for some of the answers that you are running Foxpro Dos

Firstly for speed reasons try the exe on the local stations.
Check your user rights on the server
 Check the status of the files on the server using the flag command as
Flag *.db? rw
Flag *.fpt rw

Check the set exclusive option is set to off on the config.fp and isn't
being reset to on in a program.   Check that you haven't set an flock or
rlock and left them on.
Check that the config.sys on the workstation has a files=200 statement
Make sure that you use the Microsoft Netware Client and not the Novell
client

Thats about all I can think of at the moment.

I am running a big suite of foxpro dos 2.0  and FoxproW26 programs to Novell
3.12 servers with no problems so there are solutions to your current drama
<g>

Al.


Quote:>Help.

>I am trying to run FoxPro 2.0 on a Novell 3.12 server and I am upgrading
>workstaions to Windows 95. I can get foxpro to run but I am having a
problem
>with file locking. I can use a file once and when I go to access it again,
it
>says that is in use by another person. Data & EXE on the server.

>Help. If I can't solve this one there may be an opening for an Analyst in
>Buffalo!!!

>Chuck

 
 
 

FoxPro 2.0 Lan

Post by Dick Walke » Wed, 25 Aug 1999 04:00:00


Hi,

chances are the file has been left open and when you try to use it again you
are getting a "file in use" error. If that is the case try putting the file
opening code in an if statement like:
if used('<file name>')
   select <file name>
else
  use <file name>
endif

If you do have other users and the code wasn't written with multi users in
mind you have a moderately large task ahead of you. You need to set
exclusive off, then lock all records when updating them and lock files when
doing global updates.

Best of luck...

Dick Walker

(remove nospam.)


Quote:> Help.

> I am trying to run FoxPro 2.0 on a Novell 3.12 server and I am upgrading
> workstaions to Windows 95. I can get foxpro to run but I am having a
problem
> with file locking. I can use a file once and when I go to access it again,
it
> says that is in use by another person. Data & EXE on the server.

> Help. If I can't solve this one there may be an opening for an Analyst in
> Buffalo!!!

> Chuck

 
 
 

1. Foxpro 2.0 LAN and 2.6 for DOS - Help for Windows 3.1 PIF settings

Wow.

It's been a long time since anyone has mentioned so many obsolete software
products in a single message. LOL

I can't help you out other than point out that the two memory standards
(DPMI and VCPI) pre-date Windows and *its* memory management and may never
be compatible. If they are compatible, great and good. It's an accident, but
a great accident. <g>

Wow ... what a blast from the past.

Dan


2. CLING; Common Lisp/Ingres interface wanted

3. FoxPRO 2.0/LAN and PC-Interface

4. Hard Code Title Case Change?

5. FoxPro 2.0/LAN Patches -- Are there any?

6. Question : SPL err_get() equivalent?

7. FoxPro 2.0/LAN and Lantastic: Problem Combo?

8. Oracle v7 versus Sybase

9. Foxpro 2.0 Lan

10. how to create libraries for FoxPro/LAN 2.0

11. Foxpro/LAN 2.0 European edition, Disk1

12. FoxPRO/LAN 2.0 - Does it work?

13. Problem With FoxPro LAN 2.0 on newer machines