Huge iAssembly control

[Anonymous]

Hi guys 

I have created an iassembly which if I had to populate all the different configurations in it, it would amount to about 300 000 different configurations. 

When changing from one assembly to another it is taking forever for the assembly to update.  I need help with some ideas on the following.

1. There are 300 000 different configurations.  Scrolling up and down the browser is going to be tedious.  Is there anyway that maybe ilogic or VB could be used here to be able to browse to the configuration I want quicker.
2. When changing to a different configuration it is taking extremely long to open up the new assembly.  Sometimes up to 30 minutes.    

The graphics card I am using is the AMD Radeon  HD 7470.

Does anyone have any ideas on how to manage this a bit more efficiently or have any ideas on how to streamline the process.

Kind Regards

Safwat 

[LukeDavenport]

I'd consider converting the assembly to be iLogic-driven, instead of table
driven - that way you can generate the required configuration on demand by
entering some values in an iLogic form in the assembly.

[Anonymous]

We have considered this.  One thing is that we have got all the information in a spreadsheet already ( 300 000 configuratiojns) so we would like to utilise this if possible.

[LukeDavenport]

Ah I see. In that case use iLogic to perform a lookup from your existing spreadsheet (by single or multiple values) to find the specified configuration, read the rest of the values into the assembly from the spreadsheet, and drive down the parameters to the relevant parts using iLogic. This method generally works really well.

For a spreadsheet with 300K rows, you'll have to test out the standard iLogic 'GoExcel' snippets to see how fast they are. If they're too slow, use a decent .Net method in your iLogic rule (read all the data into a single array, not one row at a time!)

Hope this helps.

Luke

[Anonymous]

Thanks Luke

I will try this out

[Ruffy85]

use Sql for that!