I deal a long time with the problem of freezing the application when using Dir() or FileSystem object.

Thanks.

from the netherlands

The main application could simply check regularly the external ‘Result’ table and display a permanent progress bar until a result is returned.

I’ll think about this and try to implement it some time. Don’t have the time just now though ;-(

Another, more simple solution would require a an external program or Access database already containing the necessary code and shipped with the application. Until now I’ve always tried to make my utilities from the principle that they should be created from within my main application, but it may be smarter to just create these ad-hoc tools separately and ship them with the app.

Using external programs is actually an easy way to deal with blocking code. For more general asynchronous coding it’s actually more useful to use .Net or addins.

I have been looking for answers like this and never found one really this good.

This forces me to ask another question. . .

Can you create code like this to see if a SQL server is found, and to see if the database is also found, or maybe retrieve a server list and database list from SQL.

That will be really great to have. . .

Imagine the code can say, looking, maybe even with a progress bar, and not hang the application.

The access somtimes says not responding, misleading users, this wasy it will be more proffesional. . .

Good Idea, inst it?