Rewrite adp / sqlserver access to C # .net?

I am not a technical person and I have a small company that has been supporting the software of my companies for several years. The solution works well, and reshuffling the solution has been with the current IT service provider for over 15 years. I recently got a better-known IT firm for conducting a general software audit. The current solution uses access as an external interface with sqlserver 2005 as a database. The company that conducted the audit presented a list of errors, among other things, that the technology is outdated, the solution does not scale, poor design, user-friendly interfaces, tables are not standardized, tables do not have referential integrity, do not use proper coding standards and naming conventions, security only for application security, etc. The company that conducted the audit,suggested that the decision be rewritten and proposed to do so. The current service provider recognizes some of the results, but assures me that it has very little or no risk to my business. Recording an application will cost a lot of money. I am in a difficult situation and would appreciate technical advice. I basically need to know if my business is running on current technology. I currently have no more than 70 concurrent users working on the systemI basically need to know if my business is running on current technology. I currently have no more than 70 concurrent users working on the systemI basically need to know if my business is running on current technology. I currently have no more than 70 concurrent users working on the system

+5
source share
7 answers

Well, if you value Joel word , I would say that you really take a chance here.

Rewriting the material was and will never be safe for the company.

+3
source

Before proceeding to consider the problem from a technical point of view, you must evaluate how important the application is to your business. It sounds like you have a live app. If it provides consistent behavior and you don’t need an upgrade / new development, you can leave it alone. We, software developers, love complaining about everything else, rewriting other work with "elegant" solutions. It means money.

, , dis-array, , . , . , 15 , , .

, , , "-" , . , , Excel .. , , .

, , , , , . , , promises? , "", , , ? , .

+2

, :

  • ? , , ? ?

  • , , ? , , , .

- , , , . , - , , .

, - , -, , , , .

, , , - , , "", , .

+2

. , , , .

ADP / - Access, .

, , , ( , , , RI).

- , ( , RI - ).

Access ADP . , , - , , . , ( , ).

+2

, " -", /sql-. -.

- MS Access/SQL Server - #/ASP.Net. , , , .

70 , , , , , , . , " " " " - .

.

+1

? ?

: : 70 Avg. Hrs /: 2 () /: 8,00 ( ) /: 250 ( /)

: 70 * 2 * 8 * 250 = 280 000 / ( 500 .)

? 5%, 10%, 25% ? 50K, 100K, 200K

, , , , ? : 90%, 75%

+1

... "" Access SQL- . , .

, . - , , , . , .

  • , Access (: , )?
  • ?
  • , ?
  • 1 2?
  • Access?
  • #

, CBA:) , CBA, , . , .

0

All Articles