Reasons to use Data Access Pages or Access Forms in favour of C#?
-
I am in a small project about an application about storing, monitoring and pricing orders. I am completely in charge of the project (from analysis to tests) and I have 3 months in total to complete it (so think of about 1+ month of programming and some more weeks of fixing bugs and adding features during the test period) with 30 hours/week at most. The company is small. The budget for new technologies is almost inexistent (they will barely afford to increase server's ram from... 128MB(!) and possibly upgrade an old win2000 machine). They want a specialised client fitted to their (quite limited) needs. I know C# and ASP.NET (not an expert, but I do have experience in various projects). As the users will be few and non-concurrent, ASP.NET was simply not worth the effort (they are not thinking of working over internet). I could have a simple Access database (back end) and leave to the chief manager a front end with graphs+reports on how to make his own graphs to observe whatever he wants to, and do all the rest of the application in c# clients. But some advised me of doing everything in Access Forms. I checked this a bit more, and show that possibly Data Access Pages is a better idea. The questions are: -are Data Access Pages going to be faster in the development? They seem so with their close integration to access, but then i fear that messing with VBScript will slow down the process (I dislike scripting languages) -is Excel integration (as it will be helpful for pricing) in Data Access Pages strong enough to make up for the lost advanced GUI functionality I can have with WinForms? In both cases some pretty advanced (think of DataRepeaters on drugs) functionality will be welcome if it's easily implemented. The back end database could be used with other clients even if the company expands within reason (turning from micro to large is not even in the business plans). --Victory, Not Vengeance
-
I am in a small project about an application about storing, monitoring and pricing orders. I am completely in charge of the project (from analysis to tests) and I have 3 months in total to complete it (so think of about 1+ month of programming and some more weeks of fixing bugs and adding features during the test period) with 30 hours/week at most. The company is small. The budget for new technologies is almost inexistent (they will barely afford to increase server's ram from... 128MB(!) and possibly upgrade an old win2000 machine). They want a specialised client fitted to their (quite limited) needs. I know C# and ASP.NET (not an expert, but I do have experience in various projects). As the users will be few and non-concurrent, ASP.NET was simply not worth the effort (they are not thinking of working over internet). I could have a simple Access database (back end) and leave to the chief manager a front end with graphs+reports on how to make his own graphs to observe whatever he wants to, and do all the rest of the application in c# clients. But some advised me of doing everything in Access Forms. I checked this a bit more, and show that possibly Data Access Pages is a better idea. The questions are: -are Data Access Pages going to be faster in the development? They seem so with their close integration to access, but then i fear that messing with VBScript will slow down the process (I dislike scripting languages) -is Excel integration (as it will be helpful for pricing) in Data Access Pages strong enough to make up for the lost advanced GUI functionality I can have with WinForms? In both cases some pretty advanced (think of DataRepeaters on drugs) functionality will be welcome if it's easily implemented. The back end database could be used with other clients even if the company expands within reason (turning from micro to large is not even in the business plans). --Victory, Not Vengeance
Ok, I suppose nobody came up with a reason to use DAP over c# :P