>After some considerable time of trying to do some REAL programming with VFP 5.0;
>I've come to the conclusion that this is really a micky mouse platform.
>
>The type of thing that I'm trying to do, is to join two tables together; list the records in a grid;
>select a record; call up another form that does editing or add to the underlying database.
>
>However I'm confronted with problems at various stages.
>
>1) Using SQL Select from where then using ADDObject('Grid') to create the grid.
> The problem here is that the record pointers are not updated when selecting a record
> ie: The first record is always selected.
> Therefore the second form can only change the first record. Adding a record works.
>
>2) Adding the tables to the dataenvironment. The Grid component can only display records from one OR the other tables. At this level there is no way to join them together.
>
>3) Creating a View.
> Works fine untill an append blank is issued to an underlying table. Of course the table is locked.
>
>I cetrainly do not wish to add redundant fields to my tables. Should the user wish to make
>changes to the data they should not be forced to run cleanup routines so that all the related
>tables are also updated.
>
>It seems to me that Microsoft have forgotten about NORMALISATION.
>
>I've worked with DELPHI for some time :- REAL PROGRAMMING IS CAPABLE IN DELPHI.
>
>Everything that I've outlined above is CAPIBLE of being carried out in DELPHI.
>
>Please don't tell me to upgrade to VFP5.0a. My COUSIN is Microsoft's Product Manager
> (development software)
>here in South Africa and he can't even deliver a promised upgrade after 4 months.
>
>There seems to be something wong somewhere.
>
>Looks like it's back to DELPHI.
>
>If you can help I'll be grateful.
>John
Just one thing: all your problems can be resolved easily in VFP. Now, having this knowledge, you can return back to Delphi.
Edward Pikman
Independent Consultant