Creating a program for my company

[Lambro]

I'm using SQL Server 2000 for a backend. I would like to create a web based system using ASP. Would this solution be logical or should I stay away from a web based system? I'm looking to have Bill of Materials, Purchase Ordering, Invemtory of stock using locations and a barcode scanner. Any input would be great, Thanks.

 

[Tarwn]

It depends on your alternatives. Having a web-based interface is nice because you only have to make an update in one place to update the interface everyone sees rather than on everyones machines, you can integrate in your Domain NT user accounts, you can set it up so that certain people only see certain portions of the site dependant entirely on their NT login, etc.

What other alternatives have you considered? Note: I will probably push you towards the ASP solution just because I like web development so much

-Tarwn _{01010100 01101001 01100101 01110010 01101110 01101111 01101011 00101110 01100011 01101111 01101101}
^{29 3K 10 3D 3L 3J 3K 10 32 35 10 3E 39 33 35 10 3K 3F 10 38 31 3M 35 10 36 3I 35 35 10 3K 39 3D 35 10 1Q 19}
Get better results for your questions: faq333-2924
Frequently Asked ASP Questions: faq333-3048

 

[Lambro]

thanks for your input, do you know where I could find information on inntergrating NT users in the database?

 

[Tarwn]

I'm not sure how much you know about ASP, so forgive me if I repeat anything you know already.
ASP Pages run off IIS on a windows server (there are other options, but...). Generally the default configuration for IIS is to allow everyone in as some default NT user set up specifically for the web server. What you can do is change this setting (in the Internet Services Manager) by unchecking the anonymous login in permissions. What this does is forces the user to log in with their NT user name.

So that gives you the users NT username, and now we need to check it against the db. Unfortunatly I haven't actually created a large system like the one your trying to create with multiple levels of NT Users, but one possibility would be to set up a couple standard NT usernames for different levels of access or areas of access and then tell only the people that should have that level what the passwords are. This will limit the number of NT Usernames you will need to keep track of.

You may want to ask aroud the ASP forum to see if anyone else has attempted to load a large list of NT usernames into a local database, there ought to be someone there that has tried.
Someone may even come up with an alternative solution that would work out better for you, as I generally answer these posts after a minimum of 9 hours brthing pulping fumes, I'm not always altogether

-Tarwn _{01010100 01101001 01100101 01110010 01101110 01101111 01101011 00101110 01100011 01101111 01101101}
^{29 3K 10 3D 3L 3J 3K 10 32 35 10 3E 39 33 35 10 3K 3F 10 38 31 3M 35 10 36 3I 35 35 10 3K 39 3D 35 10 1Q 19}
Get better results for your questions: faq333-2924
Frequently Asked ASP Questions: faq333-3048

 

[KenHN]

Hi,

You can look into thin-client computing. It is low cost and most terminal has a small foot print that you can easily install on the factory floor.

What you need is a terminal (WinCE Terminal), a display and scanner for data collection on the shop floor. backend u can used Win2K. To link up, use Terminal Service Client. You can configure a Application Server on Win2k. Just develop your app using VB with SQL database on the server, and the client can log onto the server through terminal service.

For more info let me know

Ken