Ivan,

Thank you very much. I appreciate your detailed description. I will print it and read it carefully (I am in the middle of putting out a couple of fires <g>). I am sure I will have follow up questions. Hopefully this discussion will be helpful for others as well.

Again, thank you.


>Hi there Dmitry.
>
>This is a great example to help resolve some of your questions. In the example you gave, you could have a form up and running extremely fast. Here are the steps and what StrataFrame would do for you. I will just give you a step-by-step to give you a better perspective.
>
>1. Create a StrataFrame WinForms projects
>
>2. I would then create two business objects and name them accordingly (i.e. CustomersBO and InvoicesBO)
>
>3. I would then open the BO Mapper (a tool which creates strong-typed field properties of the table on the BO) and map them to the tables of which they represent
>
>4. Next I would create a MaintenanceForm (this is a StrataFrame template that already has their Gradient Form Header and a Maintenance Form Toolstrip on it).
>
>5. Since Invoices is probably a child of Customers, I would establish the relationship between the two of the (StrataFrame will automatically manage the relationships including the foreign keys and new records…..major time saver!!!)
>
>6. Now I would drop on two business objects on my form
>
>7. I would add any text boxes and labels to the form. StrataFrame has zero-code data-binding so you can, for example, select a text box and choose which BO and field will be bound to the control.
>
>8. I can then run the program and create new records! By default StrataFrame will automatically manage your connection strings for you, so if one cannot be obtained when the application is run, their Connection String Wizard will appear. You can obviously manage this yourself too if you like.
>
>9. Next, you can drop on the StrataFrame BrowseDialog control. This control lets you create dynamic browse dialogs without having to actually write a browse form yourself. Just pick which fields you want to allow searches to be executed on, etc. and how you want the returned results to look….this is one of the StrataFrame controls which is 100% unique and will save you a ton of time!!! You can then attach it to the maintenance form toolstrip already on the form and a Browse button will then appear on the toolstrip. Run the app again and you can then browse, edit, delete, etc. You are basically done at this point other than maybe playing with the UI controls or dropping on the StrataFrame application themes control or something just to have glass effects,etc.
>
>10. And on the top of this all, although you didn't mention, I would just integrate the Role Based Security module (RBS) into the application, which has very professional features, ready to integrate into any StrataFrame application.
>
>You do no have to program all of the save, undo, edit, and delete logic….it already exists. The MaintenanceFormToolstrip ties into the UI and the BOs to provide this functionality by literally just dropping it on the form! The nice thing about StrataFrame though is that it is very extensible meaning that you can programmatically do or overwrite just about anything to do it differently if you have the need to.
>
>Hope it helped.
>
>Ivan
>
>
>
>>Hi Ivan,
>>
>>As I mentioned, I am interested to learn more about how StrataFrame works in a high-level overview. Maybe if I give a simple example of a very small sample app you can tell me how you would use it there? Let’s try:
>>
>>The purpose of this “imaginary” application is to post invoices. The database will have two tables: a table of customer and a table for storing invoices. The application will consist of just one window: Posting Invoices. The window will have the following fields/controls:
>>
>>Date:
>>Customer:
>>Invoice #:
>>Amount:
>>
>>The window will have a button to [Add Invoice] [Save Invoice] [Cancel Save]
>>
>>What I am interested is to know are the steps (descriptive) is to how would create this project in VS2005 where the SF would come into play.
>>
>>For example, I see these steps:
>>1 – Creating Window App.
>>2 – Creating Form
>>3 – Drop label and textboxes controls on the form
>>and so on. My question is where do you “plug” or “use” classes or methods from the SF?
>>
>>Hopefully my question makes sense to you. If not, let me know.
>>
>>Thank you.