I want to create an application that accesses SQL Server backend(s) to support multiple databases of the same structure for multiple custoners. The app will provide a frontend that will be used by dial-up and, eventually Internet users. The frontend will allow the use to login, select predetermined reports, produce an Excel spreadsheet for each report and email the spreadsheet to the user or otherwise allow the user to download the spreadsheer.

I am confused as to the relative advantages of various solutions. For example, I could write the frontend in VFP, including the queries to SQL and then write the output to Excel... or I could write the show thing in Excel... or in VB. I could use VBA with/without ADO(?).

Our technical abilities lean toward VFP as opposed to VB. But we are going to definitely move toward VB because of plans to develop this as a web page.

It is not clear to me how and when to use ADO or VBA and how those tools relate to each other. I have done some research, but it has proven to result in even more confusion than answers.

Is there a recommended solution path to do this?

Any input on this would be welcome.

Thanks, Bob