General information
Category:
Forms & Form designer
Like I said, it's monday...
OK, now I understand how you use INSERT INTO. I guess that you defined your rules in the view, that's why you can't use APPEND BLANK. I've allways defined my rules on the table, not on the view. That's why I could use APPEND BLANK on the view.
>>So you do a INSERT INTO with blank values for all fields. What are the advantages of using INSERT INTO vs APPEND BLANK in that situation?
>
>No I don't. But I do insert with fields that require a value as defined in my database constraints.
>
>>Using INSERT INTO means that you have to include one value for each field of the table in the right order
>
>No, no. You can use INSERT INTO with whatever fields you want in whatever order. For example, if I have defined a rule for a field in the DBC() such as !EMPTY(field) then I *have* to use INSERT INTO (field) VALUES (value) because APPEND BLANK will generate an error.
Previous
Next
Reply
View the map of this thread
View the map of this thread starting from this message only
View all messages of this thread
View all messages of this thread starting from this message only