First, this syntax:
<pre>INSERT INTO <table name> FROM ARRAY <array name></pre>
Is not standard SQL, and it would only work (I think) on Visual Fox, and I guess this is Visual Basic (you didn’t mention the language being used).
Second, to use this constructor of the OleDbDataAdapter class you have to use a SELECT statement. An insert statement can be specified for the InsertCommand property, but it won’t be executed when instantiating the object.
First thing I noticed was that the target database pointer had no slash after the D: in it. Indicating a full path, not an offset of the currently active directory on the D; drive.
This could be because the slash gets lost when you enter it into this forum text box.
Reason I mention it is because, you could end up with a database copied to the subdirectory of the active directory on the D drive, or the routine will not work because it can not find the table pointed to and will throw up an error. Do you catch any errors produced? (You never mentioned error reports)
Is nothing happening because the table has not been opened?
I guess you open the table at the beginning of the whole application. So, does it remain open, or does another sub close it before this sub can write to it?
as a starting point, I’d suggest opening the table, do the write and then close the table all in the same sub.