>Hi,
>
>
>I'm working on VFP DBC, where structure frequently change,let's assume there is employee information.
>
>EMP.DBF
>
>CID (PK)
>SSNO (SK)
>EMPNO (SK)
>ELNAME
>EFNAME
>EMNAME ..... 100 others fields.
>
>
>These strucuture always change.(Some time in one release 3 to 4 time)
>I'm updating information using views lv_EMP.IF strucuture expand, I have to change table & view.At client side sometime views curruption occurs or sometime view is not saving information into data.so What I'm thinking is change structure.
>

Interesting idea, but I think it's more work than you really need to do. Changing table and view structure at the client side is a conquerable task for a VFP developer with the right tools. You might look into Stonefield Database toolkit, which will build a prg for you that updates client data structures. SDT will work with views as well.

The problem with views is that views built from "SELECT *" need to be rebuilt when new fields are added so the new field information can be built into the view definition. I handle this by making all my table structure changes in a prg, running EView on all views built from the affected tables, and generating view rebuilding code. I then send the ALTER TABLE code and the CREATE SQL VIEW code to the client, who can run it once to update the table structures.

If you data structure is really changing so often depending on needs, you might look into a more flexible data structure (maybe one that goes down instead of across), but I think that XML might be overkill for this...