Managing data from a DB is a completly different ballbark. With a DB you cannot fill your table directly. You rather have to query your data and then loop over the results inserting them row by row. Am I right?
So unfortunately your hint would lead to a different direction. My data source is XML.
(Excel I have never tried. From what I hear you'd have to find a Microsoft-ODBC-driver for Excel. Sounds to me that the rest would be the same as with a DB.)
I just finished some experiments with input-XSL and output-XSL. Apparently that has no effect.
The new relative position of the rows is exported. That is: if I move a row up than that will show up in the export XML.
But if a add a row at the end this row will not be exported.
I had a similar issue with a customer I helped recently. His form was connecting to an Access DB. What I found was that when I added the new instance and performed the insert into the DB it did not seem to work. I found that I had to have the DB closed and had to reopen it to see the change. I am not sure if it works the same way with Excel. I also found that I had to have all fields filled out. For example my form/DB had FirstName, LastName, City, State, Zipcode. I had to have data in all fields. This could have been the way the DB Was set up in that it did not allow for a null value. One last thing I did was instead do using exportData I used a SQL insert