Dear SQL'ers:

Enough playing in the guts. Now, I need to figure out which
language or language to use for front-end code. The system being
planned is for a small company, and the system must be easily
modifiable.

What are your suggestions, and how does one get strated with your
suggestions?

My Wish List:

I strongly want as much intelligence in the database as possible.
Using the DBMS as merely a filestore is not acceptable.

I would like a language that has a good development environment,
including a source-level debugger. Interpreted code is just fine with
me, but it is not a requirement.

It should catch lots of errors. C's (generally) ignoring of
signed integer overflows is the wrong direction.

It should not suffer from architecture astronauts. Java is a
culprit here.

One of the people who will eventually be programming for the
system being planned likes Microsoft Access. Will it do?


So what do you suggest? What questions am I not asking that I
should?

Sincerely,

Gene Wirchenko

On Thu, 14 Jul 2011 15:39:51 -0700, Gene Wirchenko <genew (AT) ocis (DOT) net>
wrote:

I forgot the most important point -- fish, water? -- that it
should have good and easy forms handling.

Sincerely,

Gene Wirchenko

Gene Wirchenko (genew (AT) ocis (DOT) net) writes:
I don't think this is a topic for this forum really. But if you want a
heated discussion there are lot of places where you can stick your
nose in.

Personally, it seems to me that the natural choice is .Net. Whether you use
C# or VB .Net is secondary choice, although I prefer C# myself.

You mentioned Access, and all my knowledge about Access are the questions
I see from Access programmers in the SQL Server forums. As I understand
it, Access is extremely good if you want something up and running quickly.
But I wonder whether it is an environment you can grow in? .Net also has a
strong point on RAD (Rapid Application Development) features, but it can
also be used for big Enterprise multi-tier solutions.

Then again, you have a background in FoxPro, and one my client has a big
SQL Server application where lot of the client code is in FoxPro, even
though if they are moving to .Net.

--
Erland Sommarskog, SQL Server MVP, esquel (AT) sommarskog (DOT) se

Links for SQL Server Books Online:
SQL 2008: http://msdn.microsoft.com/en-us/sqlserver/cc514207.aspx
SQL 2005: http://msdn.microsoft.com/en-us/sqlserver/bb895970.aspx

On Fri, 15 Jul 2011 11:05:10 +0200, Erland Sommarskog
<esquel (AT) sommarskog (DOT) se> wrote:

Well, if I am going to be seriously using SQL Server, I need a
platform for the front-end.

One of my co-workers has put together a number of feeder apps to
my app. He has written them in Access.

I will take a look at .Net -- I have not worked with it
previously -- and skip on VFP if I can.

Sincerely,

Gene Wirchenko

I would recommend you visit:

www.asp.net -- click on MVC on the top bar. Install the FREE Visual Studio
Express (which is 100% fine for what you're building). Then, follow a
couple of the complete, end-to-end examples. You will see how the entire
system works from front-end to SQL backend.

Kurt



"Gene Wirchenko" wrote in message
news:a801279di01poqckhrjlelgi976nssk42o (AT) 4ax (DOT) com...

On Fri, 15 Jul 2011 11:05:10 +0200, Erland Sommarskog
<esquel (AT) sommarskog (DOT) se> wrote:

Well, if I am going to be seriously using SQL Server, I need a
platform for the front-end.

One of my co-workers has put together a number of feeder apps to
my app. He has written them in Access.

I will take a look at .Net -- I have not worked with it
previously -- and skip on VFP if I can.

Sincerely,

Gene Wirchenko