Web design with Access front end and SQL back end 1

[lifesupport]

I'm transferring a desktop application to a web application. This application utilizes a lot of foxpro SQL statements, so converting this to SQL probably won't be a problem. The desktop application is written in VFP so it's not designed to be multi-user. Since user's will be making selections thru the reporting process and these selections will result in the development of temporary tables, I thought it best to have these temporary tables in Access on the client side. This would help keep the app as multi-user. Also, I don't want to send large amounts of data over the internet as that's probably inefficient with $$ and speed. I thought perhaps I would use Access tables on the client side to save the table results from the client's selections and SQL on the server side where the pulling of data (from larger tables) will take place. Can this be done? If so, what does the client need (if anything) on their side for this to work?

Thanks

 

[johnwm]

I see from your profile that you seem to have been working on this since at least May 06 (thread1253-1222786). I suggest it's time to grasp the nettle and start to do this properly, rather than stumbling on with a botch job. Start with a properly designed database on either MSSQL or MySQL and develop your front end in either ASP.NET or PHP.

If you are a dedicated MS shop, and don't mind spending money, then you can go with MSSQL and ASP.NET - otherwise go with MySQL and PHP. I would generally avoid storing any data (other than cookies) on the client. Just serve each query direct from the DB via an appropriate stored procedure.

If you have any specific questions relating to the code, post your question in the appropriate forum.
forum434
forum436
or the MS equivalents

If you want the best response to a question, please check out FAQ222-2244 first.
'If we're supposed to work in Hex, why have we only got A fingers?'
Drive a Steam Roller