see my last post - add the dbfailonerror bit, and it will show you what is wrong with the sql
with regard to your last post
what does the vbnewline achieve - this just CANNOT be correct
vbnewline certainly has nothing to do with problem as it already did before adding newline-characters (which is what vbnewline does). At some point I thought maybe VBA cant handle long string without linebreaks so i added them later, but without any help. I know what is wrong with the SQL when it executes. If you build a query and it fails to include ALL STRINGS then certainly a query is generated that is not valid. The question is why does VBA not execute all code correctly, not whats wrong with the query.
Dont think re-installing Access will help, because it fails on both XP and Vista business machine. Both with newly created MDB's. So wouldnt it would be rather strange that my app destorys Access on 2 machines with different OS?