That's a good question. My philosophy, when a db of mine
will run on multiple platforms, is to use code that all
versions of Access will understand, even if it's a little
slower or more cumbersome. Access XP provides some great
new methods, etc., that I love to use, but a lot of people
don't have XP. I've run into problems many times with
neat methods that older versions don't understand
(filedialog, openargs for reports, move vs movesize, and
so on. I would go with the DoCmd method.
As for why it's better to use the Application method if
possible, MS says "The Echo method of the DoCmd object was
added to provide backward compatibility for running the
Echo action in Visual Basic code in Microsoft Access for
Windows 95. It's recommended that you use the existing
Echo method of the Application object instead." They
don't say why, but I assume they know what they're talking
about.
Hope this helps!
- Scott
-----Original Message-----
Thanks Scott,
Actually, my users would be running a runtime application
(no Access on their machines). The app was developed in
Access97, but I have been able to use the Application.Echo
True/False commands (at least I think I have). Should I
just revert to DoCmd.Echo for my application? What is the
advantage to Application.Echo?