The database and code is ready to go but I would like to hear what peoples
thoughts and opinions are as to what programming language is best to use for
the web interface and why? Should I use Java, C, C++, C#, etc.
All replies are greatly appreciated.
Thanks,
FatMan
What is already in place? Do you already have a web server or will you be
setting up a new one? If an existing one you will need to see which of
those it will support and which would require changes.
Which technology/language are you already familiar with? That would be the
best choice. If you are familiar with none of them I'm sure
representatives/advocates of each would provide many reasons why their
preferred platform is the one you should use. I imagine that ASP.Net would
be among the easiest to learn from scratch. At least for someone already
famiiar with other MS development tools.
--
Rick Brandt, Microsoft Access MVP
Email (as appropriate) to...
RBrandt at Hunter dot com
Yes, it is a new web server and whatever language will be used to complete
the interface between the web and my existing access database will need to be
learnt. I have done some searches at the local (Canadian)
universities/colleges and have found courses being offered in Java, C, C++
and C# but not ASP.net. As I have said I have searched Canadian
universities/colleges for online courses but do not/will not limit myself to
Canadian schools if someone knows of a good language and course to go with it.
Do you know of a good course in ASP.net?
Thanks,
FatMan
--
Best regards,
___________
Alex Dybenko (MVP)
http://accessblog.net
http://www.PointLtd.com
"FatMan" <Fat...@discussions.microsoft.com> wrote in message
news:6EFCAFD2-3EC5-404E...@microsoft.com...
Thanks for your comments,
FatMan
"FatMan" <Fat...@discussions.microsoft.com> wrote in message
news:C021DFB4-B764-40A5...@microsoft.com...
> I have a database program that I would like to add a web interface
> for. That is to say I would like users to be able to navigate to
> my database through the web, log into the interface and
> add/modify/delete records that pertain only to them.
Are you sure that hosting it on Windows Terminal Server and allowing
them to run it via Remote Desktop would not be a much, much easier
approach? There are RDP clients for even non-Windows OS's. For those
users, it would be a bit more complicated for the users than using
their browser, but it would require no development work whatsoever
to deploy it.
--
David W. Fenton http://www.dfenton.com/
usenet at dfenton dot com http://www.dfenton.com/DFA/
Well with .net you would be programming in one of the CLR languages of which
C# is one so a C# class would aid you in developing an ASP.Net solution.
When dealing with web development you are actually learning a whole
collection of new skills. The programming language being just one of those
things.
I guess a Windows Terminal Server would be much easier to implement but how
would we handle the printing of reports. I would most likely have 50 users
and they will want to run the reports and print them at their remote
location. How does Terminal Server handle the printing back to the client?
You also mentioned non-Windows OS's RDP clients...can you name a few or point
me in the correct direction?
Thanking you for your help.
FatMan
> I guess a Windows Terminal Server would be much easier to
> implement but how would we handle the printing of reports. I
> would most likely have 50 users and they will want to run the
> reports and print them at their remote location. How does
> Terminal Server handle the printing back to the client?
The server has to have a printer drivers installed on it that are
compatible with the local default printer. If that's already in
place, the user does nothing -- by default the printer on the server
gets mapped to the local default printer. The problems come when you
have to support users with a bunch of exotic and various printers.
In a satellite office situation, it's much simpler, as you know what
the local printers are and can easily install the drivers for them
on the terminal server.\
> You also mentioned non-Windows OS's RDP clients...can you name a
> few or point me in the correct direction?
The MS website provides the downloads for non-Windows OS (just as
they do for Windows).
I ran into a similar situation a year or so ago. Instead of printing, I set
up the forms to allow the emailing of reports to the user. This way, they
can print, save, forward, etc. the report. I used Stephen Lebans email code
which is just awesome to covert documents into PDF.
I use the RDP setup with nearly 70 clients. However, to make it appear
"weblike," my clients visit my website, select a button which opens up the
RDP connection.
Although sometimes it may be nice to just print right from access, most of my
clients like the ability to save the document for future reference or to be
able to forward the document to other collegues.
Hope this helps.
BH
--
Message posted via http://www.accessmonster.com