Accessing file on shaerd mapped drive (windows)

29 views
Skip to first unread message

glh

unread,
Nov 25, 2009, 12:56:26 PM11/25/09
to OpenQM
Hopefully just missing something obvious. Simply want QM to be able to
'see' (read/write) a file on a windows shared mapped drive. I have
tried all sorts of permutations of what I thought the following should
be to no avail ...

VOC entry ...

0001 F
0002 shared name (ie ... z:\ or \\computer\sharedname , etc...

Thanks

Martin Phillips

unread,
Nov 25, 2009, 1:00:55 PM11/25/09
to ope...@googlegroups.com
Hi Gary,

> 0001 F
> 0002 shared name (ie ... z:\ or \\computer\sharedname , etc...

This should work fine but the NETFILES configuration parameter must be set
to enable remote access (See the QM Reference Manual). This is because there
are potential locking issues that QM cannot resolve.


Martin Phillips
Ladybridge Systems Ltd
17b Coldstream Lane, Hardingstone, Northampton, NN4 6DB
+44-(0)1604-709200

glh

unread,
Nov 25, 2009, 1:31:17 PM11/25/09
to OpenQM
Hi Martin,

I had already set NETFILES to 1 (or does it need to be set to 2) with
the same results.
Anything else I should be looking at?

Thanks,

Gary

On 25 Nov, 11:00, "Martin Phillips" <martinphill...@ladybridge.com>
wrote:

Martin Phillips

unread,
Nov 25, 2009, 2:45:39 PM11/25/09
to ope...@googlegroups.com
Hi Gary,

Try a simple program that attempts to open the file and print the values of
STATUS() and OS.ERROR() in the ELSE clause.


Martin

CDMI - Steve T

unread,
Nov 25, 2009, 3:56:53 PM11/25/09
to ope...@googlegroups.com
why set a 'mapped drive' ?
why not just:
 
READV MAPPED.DRIVE FROM PARAMETER.FILE,MAPPED-DRIVE,1 ELSE
 MAPPED.DRIVE = "\\CDMI-WEB\CDMIWEB_F\QMSYS"
END
**** something like that above... then
OPENPATH MAPPED.DRIVE TO FILE ELSE
 CRT \Could not open \:MAPPED.DRIVE:\ status \:STATUS():\ os.error \:OS.ERROR()
 INPUT DIO
 STOP
END
 
what do you benefit from a mapped drive?
 
Steve Trimble
Computerized Data Mgmt Inc
PO Box 13403
Maumelle, AR 72113
(501) 803-0974 09:00am - 6:00pm CST
 
Home of self defense products: http://www.protecturself.com



From: Martin Phillips <martinp...@ladybridge.com>
To: ope...@googlegroups.com
Sent: Wed, November 25, 2009 1:45:39 PM

Subject: Re: Accessing file on shaerd mapped drive (windows)


Hi Gary,

Try a simple program that attempts to open the file and print the values of
STATUS() and OS.ERROR() in the ELSE clause.


Martin

----- Original Message -----
From: "glh" <ga...@unaweep.com>
To: "OpenQM" <ope...@googlegroups.com>
Sent: Wednesday, November 25, 2009 6:31 PM
Subject: Re: Accessing file on shaerd mapped drive (windows)



Hi Martin,

I had already set NETFILES to 1 (or does it need to be set to 2) with
the same results.
Anything else I should be looking at?

Thanks,

Gary


23 11:54:36 PST 2009 -->

Brian Speirs

unread,
Nov 26, 2009, 3:20:43 PM11/26/09
to OpenQM
Another couple of things to try:

Open a DOS box from Windows and try to list the shared folder using a
DIR command.

If that doesn't work, you've got general networking issues.

Assuming that does work, try the same thing from the QM command
prompt:

! DIR path_to_sharedfolder

If that works, then you should be able to access the data from
QMBasic, although you'll still need to work on permissions to make
sure that you can update the data.

Cheers,

Brian

glh

unread,
Nov 27, 2009, 12:48:21 PM11/27/09
to OpenQM
Hi All,

Thanks for your response(s)

(1) Does appear when responding to a DOS dir cmd

(2) Does appear when responding to a !dir cmd in QM

(3) Responds with the 3007 error when attempting to open in basic
program in QM

(4) QM version 2.9.9. Have tried setting NETFILES=1 & NETFILES=2 W
with same result.


Thanks,

Gary
> > Thanks- Hide quoted text -
>
> - Show quoted text -

Brian Speirs

unread,
Nov 27, 2009, 2:08:43 PM11/27/09
to OpenQM
OK. I've had this problem before ...

Look in the ERR.H item in the SYSCOM file. This gives the error
translations.

Error 3007 is 'No VOC record'.

So, looking back at your original post, you have defined a VOC entry -
but there is no dictionary component. So create a dictionary:

CREATE.FILE DICT JUNK

and then put a reference to that dictionary in your VOC item.

0001 F
0002 Path to data file
0003 JUNK.DIC

The file should now be accessible.

Cheers,

Brian
Reply all
Reply to author
Forward
0 new messages