Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
sanvij
Starting Member
1 Post |
 Posted - 2005-05-13 : 12:48:12
|
| We have an MS Access application (Forms, Macros, Queries, tables all in Access) as a prime business system.We want to convert Access application into latest technology, so we have suggested .NET. But, now we are in a position to convince the client why to convert to latest technology. Say, the performance, layering, security,..etc parameters are there.Anyone has a thought on this? Or if you can send me the reference docs it will be very helpful.Regards,Vijay |
|
|
ac001
Starting Member
3 Posts |
|
|
AjarnMark
SQL Slashing Gunting Master
3246 Posts |
Posted - 2005-05-25 : 11:33:56
|
| Wait a minute... .NET is only half an answer. What will you be using to store the data? Access is both a database and a client interface development tool. .NET only does the client-side. It is not a database. .NET applications can interface with many different data stores, such as Access, SQL Server, Oracle, XML, etc. So which one are you using?And why are you wanting to do this migration? Maybe that sounds like a stupid question, because I am loving working in .NET and SQL Server myself, but you are asking us for ways to justify to your client to make this move. So, is there any compelling issue such as unacceptable performance in the Access application? Or maybe you're looking to create a web front-end and Access is just murder on a web server? Is security an issue? If so, that's probably more your database security technique than your application. Or are you just antsy to get into new technology and you're searching for some possible way to convince your client to pay for your learning curve?---------------------------EmeraldCityDomains.com |
 |
|
|
|
|
|
|
|
MS Access Application to DotNet