.Compose Question

[iwells]

Hi,

Fairly inexperienced with the COMAPI and had a question about .compose method of a view. My questions are:

1) What is the purpose of this? I think the purpose of .compose followed by Array(...) is different than dblink.openview in that it "automatically" joins the views you specificy in the array and provide extra data in the view other than the base view specified in the dblink.openview? I equate this to using joins (array) rather than a simple select from (.openview) ... is my assumption correct?

2) can you "nest" arrayed views in other .compose method calls? for example, assuming I'm right in part 1 and I vGLPOST.compose (vGLPOSTO) and then use vGLPOST inside a later array does it also include the information joined from the previous compose?

If I'm totally wrong on this can someone give me a brief tutorial?

Thanks,
Ian

 

[ettienne]

Compose = link tables
I don't understand question 2 - it makes no sense to me. I'm going with no as an answer.

Sage 300 Certified Consultant

 

[Jay Converse]

1. They're not views like SQL views, they're a key part of the business logic layer. Use what you see when you record macros, and don't add or subtract anything.
2. No.

 

[iwells]

Tuba, the thing is lots of times when I open a window to record a macro there are several .compose statements with arrays, but if I look in the sage application object models I can see that the data I need isn't in the views that are being linked in the .compose. I'm trying to cut out extra code I don't need.

 

[Jay Converse]

I have 17 years of experience coding to Accpac views, and I've learned that unused views don't hurt a thing, and you never know when you'll need them later in the project.

 

[iwells]

I tend to agree with you, but I just chopped a procedure down from 200+ lines to 20 lines and there are more like this in the macros I'm editing, so it makes it very difficult to understand what's happening with some of the cluttered code.

 

[ettienne]

I'm with Jay, Compose are the least of your problem.

If you want to unclutter the code then get rid of all the Temp= crap etc.

I clean up code by moving all the Dim lines to the top, move the OpenViews together followed by the Compose lines.


Sage 300 Certified Consultant

 

[Jay Converse]

Ditto with ettienne. And get rid of the xxxfields objects, use xxx.Fields instead.

 

[iwells]

I definitely reorder the Dim statements, openviews, set statements and several other things, but I also favour removing unnecessary lines of code to make it easier to read and understand what's being used and what isn't and especially if someone else who isn't familiar with the macro has to come behind you and read it.

 

[DjangMan]

Stephen Smith's blog still has lots of useful technical information on Sage.

https://smist08.wordpress.com/2013/10/27/composing-views-in-the-sage-300-erp-net-api/