I am reading through some stuff on the MS website, which doesn't seem to cover the basics of this. I presume that this would be written in Visual Studio .NET and that there's an option somewhere that determines what the compiled project is (Website|Application).
This will see the collation of about 12 applications (in Access) each of which contains upto 75 forms with the existing web solution which has around 80 pages. The whole system can be linked to either Access or SQL databases, of which there is (presently) one DB per application.
The net result of my aims is that the final application will be fundamentally the same for both types.
The vision that I have is that the final (singular) database will be a lot more structured and "neat" with extended use of stored procedures to get the data available in a 'ready to use' format. From the application side of things; just one project to manage and develop with code that is saved on a server (under source safe). The application is then compiled to web or application to suit my clients needs.
Have to note at this point that my client base is VERY fussy about IT security and we often face the situations where we cannot use registry or DLL in any way ... such is the tightness of security that Access was chosen as there is no requirement for an install set ... just copy the MDE from a USB memory stick.
May sound like a task and a half (which it is, I know), but I am reasonably well versed with VB
, ASP, SQL and am quite creative, which I hope will ease the learning curve.