What is the best way to this?

[Rudy]

I'm building a application that will interface with SQL server. The amount
of data is not alot, but the data will need to be proccessed quickly at about
3 - 4 minutes at a time. Then Idle for 2 minutes, then procces data again for
about 3-4 minutes. The majority of the process will be client computers enter
data into the tables, and that data getting calculated in a formula, and
spitting out the return to client computer.
This will be set up on a intranet network, with a max of about 100 clients.

My question is, which isw the best way to go, build a windows application,
or use ASP.net. I just recently started playing with ASP.net,, and I love
it. Here it the other catch, it needs to look like that it's not a windows
program. No title bar or anything. I know I can do that with vb.net, but can
I with ASP.net

Thanks as always for the advice!!!

Rudy

[Diggler]

Does the end user need to interface with the app at all? Sounds like maybe
you could use a Windows Service...

"Rudy" wrote:

I'm building a application that will interface with SQL server. The amount
of data is not alot, but the data will need to be proccessed quickly at about
3 - 4 minutes at a time. Then Idle for 2 minutes, then procces data again for
about 3-4 minutes. The majority of the process will be client computers enter
data into the tables, and that data getting calculated in a formula, and
spitting out the return to client computer.
This will be set up on a intranet network, with a max of about 100 clients.

My question is, which isw the best way to go, build a windows application,
or use ASP.net. I just recently started playing with ASP.net,, and I love
it. Here it the other catch, it needs to look like that it's not a windows
program. No title bar or anything. I know I can do that with vb.net, but can
I with ASP.net

Thanks as always for the advice!!!

Rudy

[Cowboy (Gregory A. Beamer) - MVP]

You can open a browser window with no title bar, etc., if that is the desired
look, so "yes" you can do it with ASP.NET. Is it the best way to go? Not
sure. You can also deploy a windows app from a web page.

The best architecture for multiple clients is a multiple tiered architecture
where the GUI, windows or web, is very thin and most of the logic is in the
middle and data tiers. ASP.NET might be a pain if you are actually running
queries that take 3-4 minutes to calculate the answer, as the timeouts are
much shorter on web apps (you can configure this).

What I am getting at is the GUI is less important than the architecture. If
you need a dynamic GUI, it will be easier with a WinForm than a web app. If
it is not dynamic (meaning the GUI is dynamic, not the data), either will
work well.
---

Gregory A. Beamer
MVP; MCP: +I, SE, SD, DBA

***************************
Think Outside the Box!
***************************

"Rudy" wrote:

I'm building a application that will interface with SQL server. The amount
of data is not alot, but the data will need to be proccessed quickly at about
3 - 4 minutes at a time. Then Idle for 2 minutes, then procces data again for
about 3-4 minutes. The majority of the process will be client computers enter
data into the tables, and that data getting calculated in a formula, and
spitting out the return to client computer.
This will be set up on a intranet network, with a max of about 100 clients.

My question is, which isw the best way to go, build a windows application,
or use ASP.net. I just recently started playing with ASP.net,, and I love
it. Here it the other catch, it needs to look like that it's not a windows
program. No title bar or anything. I know I can do that with vb.net, but can
I with ASP.net

Thanks as always for the advice!!!

Rudy

[Rudy]

Thank you Cowboy and Diggler,

Good info, it sounds like I want to stick with VB.net. I already strated
it, just wanted to make sure I was useing the best technology. Thanks again!!

Rudy

"Diggler" wrote:

Does the end user need to interface with the app at all? Sounds like maybe
you could use a Windows Service...

"Rudy" wrote:

I'm building a application that will interface with SQL server. The amount
of data is not alot, but the data will need to be proccessed quickly at about
3 - 4 minutes at a time. Then Idle for 2 minutes, then procces data again for
about 3-4 minutes. The majority of the process will be client computers enter
data into the tables, and that data getting calculated in a formula, and
spitting out the return to client computer.
This will be set up on a intranet network, with a max of about 100 clients.

My question is, which isw the best way to go, build a windows application,
or use ASP.net. I just recently started playing with ASP.net,, and I love
it. Here it the other catch, it needs to look like that it's not a windows
program. No title bar or anything. I know I can do that with vb.net, but can
I with ASP.net

Thanks as always for the advice!!!

Rudy