In my sig, there's a link "I swear I saved my data, where'd it run off to?" ... read it, see if it's something that applies in this case.
That said, I wouldn't use CurrDir() either... there's no telling what it is... if could be the fodler where you app is, or it could be somewhere else... it's affected by the system. User application.StartupPath if you want the folder where the app is runnign from.
Also, you're looping through something, but all of the rows pull from the same text boxes over and over...which is going to result in multiple rows with the same data in it. -- nevermind, I see where the different data is. Next, after adding the row to your data tabale, DON'T call the update... at least not jsut yet... loop & add your rows first... THEN call the update...
Lastly... this isn't a good idea:
It's possible you're getting errors, but you'll never know. You've decided to stuff your fingers into your ears and yell "NYA NYA NYA" completely ignoring the fact that VB might be trying to tell you there's a problem with your update. But you'll never know unless you take out the Try/Catch, or at least within the Catch display the error. If there is an error happening, it's happening for a reason, don't you think it would be a good idea to figure out why?
Catch x As Exception