Is this for you or a user? I have a form that I slapped a grid on and the grid is populated dynamically when a table is opened. The editing is in the grid though. I use it to manually edit client tables onsite when necessary (outside of our main app). Would something like that work?
>I have dozens of small and infrequently used tables (remote SQL views) that I need a quick way to develop an ADD form. It does NOT have to be pretty.
>
>I thought of haveing a PRG that is called with file number
>Then a Case statement to open correct table.
>
>I hoped I could use only one generic ADD Form.
>Open the database before I call the form.
>Append blank at form load
>Use EDIT command to show fields (this is a new record and not yet updated)
>Put two command button at bottom Save & Cancel
>Save has a tableupdate(), Cancel has Tablerevert()
>Then thisform.release
>
>YES, this is crude but quick to build.
>
>Question: on EDIT command, can I put it on a Form and can I limit user to editing just that one record?
.·*´¨)
.·`TCH
(..·*
010000110101001101101000011000010111001001110000010011110111001001000010011101010111001101110100
"When the debate is lost, slander becomes the tool of the loser." - Socrates
Vita contingit, Vive cum eo. (Life Happens, Live With it.)
"Life is not measured by the number of breaths we take, but by the moments that take our breath away." -- author unknown
"De omnibus dubitandum"