VB Code debugging in Access
Posted on 2006-07-14
i have some code written by a colleague who has now left which takes data written into an access/sql adp and writes it into a word document.
the problem im having is that it's not producing any word docs yet is not producing any error messages when it's run, how can i find out which element is causing it to fail when the code is not actually failing?
does this make sense? normally the access debugger will immediately point to the part of code where the problem lies but it's not as it doesn't recoignise a problem but obviously somewhere it is failing.
I will add more points if need be just need an old q refunded first