Here's the only import routine option that I see via ODBC:
"If the specified object does not exist, Access will create it. If the specified object already exists, Access will append a number to the name of the imported object..."
1. Would a loop of a thousand (or more) DoEvents help or not...
Ok, I follow your logic. And I read your links you provided. I rolled up my sleeves and...
It seems there is an issue in that the new tables I'm importing are Foxpro DBF files that I import via ODBC; and I don't see that Access is able to use append this data to an existing table - it appears...
Thanks, I appreciate the advice, but I don't know how to do that. I'll need to do some reading, unless you can provide examples of what you are suggesting.
What does not seem logical to me is that it works fine 80% of the time, and when it bombs out it can be restarted out of the code break...
I created a macro for the steps I needed, then converted to VBA. I usually program in Excel which is easier because I can record many of the steps and then modify the code.
I guess the real answer to your question is that I don't know any better...
In a nutshell, I'm trying to import new...
1. I could not seem to import new tables that would overwrite the old ones, so I coded to delete the old ones before importing the new.
2. I was trying to redirect the code back to where it crashes, for when I manually debug and set the next statement and continue, the code executes just fine...
Yes, but I see "Recordset not Updatable" appear in the status bar at bottom of screen during load; after load is complete that message changes to "Datasheet View"
I wrote a macro and converted to VBA in Access/Office365, and I run this routine nightly. A few months ago it started crashing a few times a week with the error "the recordset is not updatable". If I debug and set the next statement at the line it crashed, then select continue, the routine...