Smart clients or Thick/Thin

[IxiRancid]

Hi,

 

I've been assigned to make a program that would run on our Terminal services and be accessed by up to 80 clients per work-day.

 

This is my question:

1. the software must have a report that each client prints out after the calculations are done.

Some general considerations:

Access vs. SQL - which one should I use?

Reports - Crystal or Access built-in?

 

I have this idea so far:

Make an app that at first run makes an empty insert and reserves the ID culumn which is then used for update and extracting the right report.

Start the app -> one empty record is made -> user changes settings and stuff -> inserts (which is really an update WHERE Id is id from step two) -> extracts a report (using that same ID).

 

Would this be a possibillity?

 

I'm open for any suggestions.

Thanks!

[Robby]

This has little to do with thick or thin client since users are gaining access through TS.

 

For now you have 80 users, how many at the same time and what about a year from now? For the possibility that these numbers may grow I would suggest SQL Server. You can still use Access reports by creating an Access project and linking to the SQL Server tables.

 

This does make sense since clients will not require any software installed locally.

[IxiRancid]

Yes, I forgot to mention that I am thinking of using an Intranet application, that could be served through IE... hence the Thick/thin stuff.

But, yes, serving the app through TS doesn't really make any matter.

 

I'll try some concepts and see.

Thanks

[samsmithnz]

You need to nail down a bit more what you want. Telling us you're considering a smart client, thin client and a thick client, tells us that you're still not really sure what your requirements are...

[IxiRancid]

OK, this is it:

An app for calculating Appartment Loans is curently being used by a few clients on their own PC's. Works fine - vb.net forntend, Access base + reports that print out calculated loans. Primary tables are deleted when new loan is being entered, back-end table stores all inserted credits just for review.

 

They (my company) want this app to be deployed on TS and be accessed by many clients. First problem is tables being deleted with each new entry (done with a Acc qry), second is the mass of clients (80+ per day, probably 3 or more at the same time).

I code for more than 3yrs (still a student), but I never had any tasks of programming for such a mass!

If only I had some possible scenarios, things would go more softly and nervous-less :)

 

Ixi