Cool. Send me an email or a PM.

I think that I'm gonna have to re-read that stuff a few more times before I "grok" the concept you're talking about. Maybe it's just cuz I've had a long day and I guess I'm more tired than I thought, or maybe it's because I haven't really done any VFP since the beginning of 2002 (except for my DBA app). <g>

~Bonnie



>>>>>This is fun, Derek. We should do it more often. <g>
>
>Agreed, perhaps one day I'll give you more of the story privately - you'll get a great laugh.
>
>>>>>>You want to talk about security conscious ... our customers are cops and firemen. The firemen probably don't care all that much, but the cops sure do. Web Services are not a problem for security-conscious users ... simply connect to the Web Service via https instead of http. Security issue resolved.
>
>I can't say what I want to say here. Sorry, I can say it privately, but not here.
>
>>>>>>>I don't get what you're saying here, unless it's something along the lines of using your old Forms (from your old VFP app?) to figure out what data you need to capture and to model your DataSets from that? Seems backwards to me. Database design should be the first thing you do, and your DataSets should be based on the result sets you'd get back from Stored Procs.
>
>I didn't explain myself well: we're not using any old Forms. The functionality to read/write from the DBF to the fields/grids on the form is done through "blind" class code that has no idea of the purpose of the window (sales, customer, order, etc...). The controls on the windows have properties that define the mapping to the DBF fields, when the user saves or selects a record to look at, there's underlying class code that uses these properties to connect the DBF data to the field/grid (this is nothing new or inventive - probably lots of people do this). This Form class code doesn't know CUST_NO or ITEM_NO are controls on the window - it loops through the Form.controls[] and determines what to do with each. Then there is some Form specific code (not much) that does what you'd call business logic (i.e. update the order that it's been shipped) but it's not a lot compared to the scatter/gather type concept that we classed into Forms - makes sense? Database design DOES come first, but the
>Form controls map directly to the design with no programming code other than the original class code I wrote. Makes sense?