>Just a thought, I would check to see if there was a problem with the primary keys.

Using AERROR(), thanks to Mr. Berezniker, I was able to find out that the part of the problem was a NULL value issue with a couple of non PK fields.

So, here is the next round. I have a function assigned to the default trigger for the primary key on the table I'm inserting into. If I browse the table and do a CTRL-Y to insert a blank row so I can fill in the rest of the fields, my PK field gets populated correctly. When I use SQLEXEC to insert data into the table, I get an error about the field not accepting null values. Hopefully that was clear enough. Thanks for the help that I've been given so far.