I have heard conflicting things with using a backgroundworker to do to the work I need. My issue is that I have some reports that generate information from a query to a table as well as some information that is hardcoded which is all customer specific (such as logos, letter context, signatures) and from time to time I will be providing a newer release of my database.



As these releases get distributed to the client, it will wipe out any customer specific reports as the release will only have the generic reports. What I am looking to do is house the customer specific reports in a separate database and then each time the client logs in I want these reports to automatically update with the client ones. The trick is I need this to run in the background because I dont want the client to know this is happening but I also dont want any user lag time.

Initially, I was pointed towards using backgroundworker but I have been unsuccessful in using it in access vb.

Does anyone have any suggestions?

Thanks.