I want some tables to be "global". What I mean is that I want these tables to be accessible for all applications.

How do you go about doing that? I see no options in the table builder to allow for that.

Richard,

I use global tables too, as I have a global framework on which I develop various applications. Before cranking up AREV for this job, try COPY_TABLE. In other words, create the table you want in the current account with table builder. Then COPY_TABLE the table to the GLOBAL account.

I am still confused. When you say… "Then COPY_TABLE the table to the GLOBAL account"… That is where I don't understand.

I do not understand the "GLOBAL" account. Can you supply me with an example of the "COPY_TABLE" sentence.

I also tried creating a table in the "SYSPROG" application. Then tried to access it from another application. Can't do it. I really don't want to "attach". I want it automatic, kinda like the "SYSPROCS" table is. And kinda like you can do with windows, functions and subroutines.

Richard,

Account names are just that: names. In AREV, the TCL command to make a file global was

COPYTABLE filename VOLUMEname GLOBAL newfilename (O)

In other words, Copy the attached file to a volume, putting it under account name GLOBAL in REVMEDIA, using newfilename to name the copy of the file. I think the OI version of this command from the monitor is

run COPY_TABLE "FILENAME","VOLUMEname","GLOBAL","newfilename"

followed by a bunch of flag fields. (What ever happened to options, I wonder? You'd swear a bunch of VB morons wrote this stuff. But I promised to be nice.) Unless I'm mistaken, the OI documentation now uses "database" to mean account, so even I am confused.

If all you want is to make a file global without relocating it, use the OI command Rename_Table, as in

run Rename_Table "filename", "GLOBAL", "newfilename"

Again, the documentation says "database" when others would say "account."

Richard,

And oh, yeah, about that automatic attach. In AREV, you could put a LOGON item in VOC which was executed when you … logged on! Usually, this item listed volumes to attach at logon, which is how files got to be there "automatically."

The attach process was slow on those old 8088 processors, so RTI designed "attach images" which you could load. I designed my AREV app to load an attach image at login, and to build it if none existed. I also wrote a routine to delete images, so new a new one could be built.

I know it doesn't seem like I am getting anywhere. Well, OI has a similar feature. There is an option somewhere (Database Manager/Database/Save) which builds a new database image to attach automatically the next time you start OI. In other words, OI does by default what I had to program AREV to do. This confused me in OI at first, until I accidentally did a Database/Save.

Gerald

I get what you mean now. I am familure with the "database save". I kinda wanted to avoid that method.

I wanted to get field 3 in the "SYSTABLES" to become "GLOBAL". I just thought that there were options within the table builder or something.

There are no options. GLOBAL is a pseudo account that indicates it belongs to all accounts. Applications use the DBT to decide on which files are available at a location, so even if you create on REVBOOT your files will not automatically be seen without attaching them then define_databasing them.

The Sprezzatura Group

World Leaders in all things RevSoft

View this thread on the forum...