I still have to use (but not for much longer ) VPME and xCase2VPM and I will not miss either. I will certainly not miss the quirks or the extremely tedious view generation process that takes forever to run for a simple change Or the massive list of views which contain many more fields than I actually want to query or the generation of "SELECT *" type statements which causes VFP to throw an error when the field order changes.....

To be honest, I was worried initially about SF as you code your own queries and I assumed this would be hard work. However, after using SF, it is a MUCH better approach and is extremely easy to do. Now the SF version of my VPME application is only quering the fields I need rather than some expanded list of fields created in a view generator.

I have been using SF every day now for months and I haven't found anything yet to grumble about I am really angry with myself for not finding it years ago but I am determined to find something wrong with it so I can grumble However, I suspect it will be a spelling mistake somewhere rather than a design flaw.

The best advice I can give anyone coming from a VPME background to SF is to totally forget about VPME and views. SF is in a different league and comparisions are pointless.

Just my 18 cents worth (sorry inflation).

Humm, don't think so. I still use VPME with the PSP Libraries and xCase2VPM which takes care of creating all needed views for me, and even though I have been working with views for a long time, so far I don't miss anything from VFP while working with .NET/SF. 

I do miss some VPME features I was used to, like the form's builder and others but, I am pretty comfortable with the way things are going between me and SF/.NET.

Edhy Rijo

Thanks.  I am not going to miss using Views, that is for sure.

I definitely plan to go with SF for the future.  VFP/VPME for only those apps already developed but over time even those will use SF.

Russ Brown (Using C#2010/SQL Server 2008)

Thanks for all the very helpful comments.

I am glad I asked! 

Russ Brown (Using C#2010/SQL Server 2008)

Hola Juan.

Me alegro de haber ayudado.

Ivan

Thanks a lot for the sample. I find it very usefull.

I'm sorry for wrote in spanish, I just don't think and wrote as come to my mind. Glad to see that you can understand me.

Kindest regards

Everything is possible, just keep trying...

Hi Juan.

I read the code I posted to you and noticed I didn't code some important features in it, so I corrected a bit:

Hey Edhy.

I can read it, but not really write it. I asked for help over here...

Here you are.

• Get your view ready with the Parent and all its children, remember to have the parent PK as a column in it.
• Create a new BO in your application and use the Business Object Mapper to map it. Remember that if you are used to mapping selecting the DDT as a source, with a view you will need to go straight to the SQL Server, so deploy it first, and then map it.
• Rebuild your project and drop 2 instances of the view BO on your form.
• Drop a BrowseDialog and configure it to this BO type, use one of the instances of the BO as the BusinessObjectToPopulate.
• Configure your BrowseDialog as usual. SearchFields, BrowseResultsLayout and so on.
• Go to your BrowseDialog Events and create one for BrowseDialogClosed.

In it, put some code like the following:

That should be it.

Aha, Ivan tu eres como una cajita de sorpresa, no sabia que hablabas y escribes en Español.

Edhy Rijo