🚀 go-pugleaf

Thanks again Lee for your time.
I think the problem is not with the INSERT statement, and the dilema is
circular.
I can't use null to skip a field in this scenario because the field I would
skip doesn't allow nulls... its an auto-increment field.
If I omit the field list i must use NULL to skip fields where nulls are
accepted and the data must be in the order in which the fields are
specified... data val#1 goes with field#1 etc... so, to use or not use a
field list and nulls leaves me in a no win situation.

I finally got very tired of struggling with Builder v5/Access2000 and
decided to take another route... MS SQL Server v7.0.
I was able to migrate the data and structures rather easily and was able to
learn the stored procedure language rather quickly.

A big boost for me was the ability to have INSERT, UPDATE, and DELETE stored
procedures created for me by using a wizard. *grin*

So I basically migrated the insert statement to a stored procedure and I got
no errors/no hiccups.
However, I now have to figure a way to demo my app with SQL Server.


"Lee Gan" <leegan@hotmail.com> wrote in message news:3bd44422$1_2@dnews...
> I guess I now have a better understanding of your problem. In the INSERT
> INTO statement, you have to make sure the number of fields is the the same
> as that of the database. Use NULL to skip a field if it is NULLable. If
you
> do not want to specify all the fields, use UPDATE statement instead. Lee
Gan