Specifically on Unix (hpux) but also for windows ..

I know that we can create an OS directory then create a qpointer to the
directory and the resulting name will act like the data portion of a
pick file. Read, write etc.

Is there a way to have a Dictionary for that table?

Thanks

No.

It's not a "real" file, it's a flat delimited string somewhere in the native
OS and as such cannot be associated with a lower level file.

Try creating a Dict only file in Pick and use the USING clause as in

LIST dosfile USING DICT dosfiledict WITH... BY...

Mark Brown


"dtsig" <dtsig (AT) hotmail (DOT) com> wrote

"dtsig" wrote:
Going the other way, we can make files in D3 look like Linux OS-level
files. I'm not talking about OSFI files that are really stored in the
OS, I'm talking about blob files. This allows you to access your DBMS
with shell scripts, C/C++, Java, Perl, PHP, Mono C#, etc. You can
also access data through programs as though it's coming from the file
system, just like /proc makes system statistics available.
It's not easy, but it is possible.

TG@ solutionslookingforproblemsNebula-RnD.com

Examples:
===========================
$ls dbms/customers
0001 0002 0003 0004
0005 0006 0007 0008
===========================
$more /dbms/atb
Aged Trial Balance Page 1
Client.. Invoice# 30... 60... 90...
[snip]
===========================
$cat /dbms/filesave > /dev/null
===========================
$vi dbms/customers/001
001 MyCust
002 ...
===========================
// Java:
FileReader item = new FileReader("/dbms/customers/0001");
BufferedReader custrec = new BufferedReader(item);
String record = new String();
while ((attribute = custrec.readLine()) != null) {
// do something
}
===========================
$cp /tmp/text.data /dbms/mymvfile/data.from.linux
===========================

Yes. You can do this in d3/nt 7.5.2 or D3/Linux (not sure which rls)

procedure :- (fm TDATA support)
--------------------------
There is a way to store your program's source code in the OSFI and
allow you to
compile and run object as a D3 BASIC Program.

To setup you would create a DICTIONARY ONLY file, and then modify the
DATA Level File
Defintion to point to the OSFI Path. For example:

:create-file DICT extbp 11

[417] file 'extbp' created; base = 0, modulo = 11
:

:ud extbp extbp

DICT extbp 'extbp' size = 21
dictionary-code Q
account
filename c:/extbp
attribute-type
column-width
DICT extbp 'extbp' size = 27 filed.
:

:ct dict extbp extbp
extbp
001 Q
002
003 c:/extbp
:

(on D3/Unix you would define attr.3 with the /<path_name> to the
desired directory)

----------------------

Rgds,



On Jan 26, 1:52 am, "dtsig" <d... (AT) hotmail (DOT) com> wrote:

mark, i was afraid of that. Trying to get used to missed features
moving from Universe.

thanks

On Jan 25, 12:30 pm, "Mark Brown" <mbr... (AT) drexelmgt (DOT) com> wrote:

Skypirate ..

wow .. you know i am sure that i tried that and it appeared to not work
BUT I just tried this and it does indeed appear to work. I will play
with this through the day and see how well it works.

Thanks very much

On Jan 25, 11:08 pm, "skypirate" <sing... (AT) singdad (DOT) no-ip.com> wrote:

On Jan 26, 2:44 pm, "dtsig" <d... (AT) hotmail (DOT) com> wrote:
Just note that if you're used to D3's case-insensitivity you're
actually dealing with OS data so you'll have to use the case-sensitive
file/item id.

thanks for the heads up Mike. Will put this in our testing



On Jan 26, 7:03 am, "Mike Preece" <mich... (AT) preece (DOT) net> wrote: