Ok Guys, I know that you may know how to do so and that it seems

so easy that maybe the dog or cat can do it. But I have no dog or cat.

I am a old Arev coder and have never worked in the OI before. So when you say "write a Stored_proc and stick this in here put this in there make this function grab this procures thing" guy's I am lost.

I have a basic gest of the events and scripts but the new things are

still awkward at best, (YES, I am STILL reading the Docs), So please

have patientice with me. And thanks for all of your help

But if you have an example I could really use it..

Mike

Mike,

]But if you have an example I could really use it

What would you like an example of?

[email protected] onmouseover=window.status=imagine … ;return(true)"

David Tod Sigafoos ~ SigSolutions

Cell: 503-341-2983

[email protected]

Mike,

I understand where you are coming from. I was pretty lost also until I attended the Advanced OI class given by winwin last month. Then I saw the light.

And the light was… that the "stored procedures" (i.e. functions and subroutines) that you write are triggered by "events" (e.g. CLICK on the mouse button); and the events and screen/form entities (i.e. EditTable, etc.) have "properties." Properties are like tokens (or parameters) that have been predefined by OI that are associated with different form entities (e.g. the property VISIBLE=3 will make the window be maximized). The list of properties are found in the Programmers reference which you can access from the OI help. The main two functions that you will be using are Set_Property and Get_Property which allow you to retrieve the current value of the property and change it. I hope this helps.

You might consider taking the class. I think there two more. One in August and one in September. The one you want is the first day but all three days are good. Day 2 is on DDE/data warehousing and day 3 is on Web enabling your stuff. Actually the first day on BASIC+ and events should be two days long instead of the current one day.

There is a lot to learn.

Oh yes, DSig is correct. That your question was really vague, almost as if it were carried forward from a prior question.

Tom

Mike, sorry for just throwing some code at you w/o any explanation. I'm having many of the problems you are adapting to OI - a steep learning curve. An example would be the first window containing an edit field in which there is a value you want to pass to another window. In mine it is a customer number. On this first window there is also a button with a quick event of executing a procedure, which used to be called a program in the old days, the equivalent of hanging a subroutine for pre or post processing on an AREV field. In the parameters first field I pass a code which tells my procedure what to do. In the procedure you start it out with the first line of

COMPILE FUNCTION progname(param1,param2,param3,param4) and magically the parameters you coded in the quick event show up in the program.

Then if the first parameter is a value of 'customerlookup' or whatever, I tell the program to get the value of the customer number from the first window (using GET_PROPERTY) and then issue the start_mdichild command.

After much aggravation, I have determined that it is better to use a stored procedure for each window and perform actions from there rather than trying to depend upon quick events. What the other respondents are telling you about the class is good advice - it wasn't available for me.

DSig,

Of a related window setup, i.e.

Relate the customer to the invoice and from the invoice screen

with the cust# in it open the customer form with the cust# already

inserted and his data displaying.

I know it is prob. really basic but do to the radical changes I am

really confused were everything goes and etc. Damn, wonder why

Revelation changed so much of it, prob. to be window(MS) complient

Thanks everyone.

Mike

[email protected]

Mike ..

Now there you go ..

1)Relate the customer to the invoice and from the invoice screen

with the cust# in it open the customer form with the cust# already

inserted and his data displaying.

There are two ways to look at this (actually there are probabaly as many ways to look at this as there developers on the board .

a) in your Invoice screen you could have the customer information linked so you are/could edit info in either table. You could do this in Arev. When you add a db control from the control palete to the window, select the customer table and the appropriate field name. Then in the designer menu select database and Edit Criteria. Set the selection criteria so that the relation is complete. Then any control pointed to the customer table will display and update the data as you wish.

If you look at the 'examples' database there is a stock, receipts and orders setup. Although the example is pretty primative, non-document and incomplete there are some samples that you can gleam from the code for read/write processes etc.

b) if you just want to display data you create the appropriate xlates in the invoice table to the customer table. Then add the db controls with the xlate'd columns.

1) I know it is prob. really basic but do to the radical changes I am

really confused were everything goes and etc. Damn, wonder why

Revelation changed so much of it, prob. to be window(MS) complient

No .. actually they changed things so it would not be Arev for windows. But there you go

OI is a very usable product if you don't mind the many limitations. We have created some very powerful apps and others have done the same SO ..

Ask your questions and let's try to get you up to speed.

I would suggest that you first start off looking at all the samples in Examples. Like I said some of them are incomplete etc BUT you can get a lot of good ideas from it also.

If you RUN the examples application it will come up with a screen with several examples .. look at how this is created .. tear it apart etc.

WARNING: do not run the mail example as it will just blow up if you don't have notes. This is an example of the incompleteness Everything else seems to work well .. I just paged through a new 3.7 version .

[email protected] onmouseover=window.status=imagine … ;return(true)"

David Tod Sigafoos ~ SigSolutions

Cell: 503-341-2983

[email protected]

Damn, wonder why Revelation changed so much of it…

Mike,

I believe once you get past the learning curve you'll appreciate most of the non-AREV approaches Revelation has taken. There is so much more flexibility and control now with OI. In most cases what used to be very convoluted with AREV is very streamlined in OI.

Hang in there.

[email protected]

SRP Computer Solutions

Don,

You are absolutly right. Although it would have been much easier startup. Some things could have been brought over but going into a whole new paradym requires new thoughs.

A perfect example is when someone wants to convert an app to OI (or any window product) from a dos/term product. The *believe* they should bring it over as it is. The majority of the time that just wont fly. You must re-evaluate the app from the visual to backend processes. Just making it 'windoz' doesn't quite do it. Even more so when you are writing a development tool.

And Mike .. hang in there. This will become as clear as mud (hey .. sometimes when we are scubaing we are happy/lucky to get 10 feet vis. Same here

[email protected] onmouseover=window.status=imagine … ;return(true)"

David Tod Sigafoos ~ SigSolutions

Cell: 503-341-2983

[email protected]

View this thread on the forum...