Converting Access 2k to Web

  • Thread starter Thread starter D
  • Start date Start date
D

D

Hey guys- not sure where this post fits in, so I cc'd a few other groups as
well- hope you dont mind...

I have someone creating a database for me in Access 2000 (or is it called
XP?). When it's all done, I'd like it to be online via the web. Ultimately
I'd like just an online database accessed via ASP, PHP, CGI, etc- something
(doesn't matter) but where various employees can access the thing from
anywhere and do their work. It's been quite a while since I've programmed,
and my programmer doesn't know how to make it accessible on the web. How
easy/hard is this process? Beyond just the tables and a few forms, it will
have a NUMBER of queries setup. Is this a process, or fairly simple? Is it
even possible, or, do I need to find another developer to handle it and just
create it online to begin with?

Here's one more thing- I have seen a buddy do the same thing- his work
around was just doing the virtual/desktop sharing thing. He setup a mini
'server' on his pc, so you log in via the web. Then that automatically
allows you to use the Access database via desktop sharing. This COULD work,
but I get how it's not the best setup to go with. Your thoughts?
Thanks
D
 
You have basically two options,
Easy Way: Terminal Services/Remote Desktop Connections
Hard Way: ASP
If you use ASP, all of you forms will need to be created using ASP/HTML
Basically all you will be able to do is use the tables and some of the
queries from the Access Database.
You will need an ASP capable web server to host the database and web pages.
It is a pretty daunting task, I have switched from classic access to asp
over the last 2 years.
You apps will be faster over the web, no ms office overhead.
You can look here for some direction:

http://asp101.com/
http://www.bullschmidt.com/DevTip.asp
http://www.w3schools.com/
http://www.webf1.com/ScriptDoc/
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/script56/html/vtorifunctions.asp
http://www.aspin.com/
http://www.connectionstrings.com/
http://www.iisfaq.com/
http://aspfaq.com/default.asp
 
Oh jeez- I was afraid of that. Hmmmm... can you explain how the Terminal
Services deal works? Can an employee login from home, upload some files
from their machine locally to the Access virtual database, and then enter
data as well? How does that work if there's more than 1 person using the
database at the same time? That MIGHT be an option...

Thanks for the reply and links- I'll check those out as well. My problem is
my programmer doesnt know ASP and whatnot, soo... Im stuck using him, or,
fidning someone else for the job. I'm open to either, I just need this done
asap.
Thanks again!
D
 
D,

With terminal services you would have windows server with however many
client licenses you need terminal services. A user would access the server
over the web and log in, just as they would to a Windows Domain. Each user
would have a profile on the server with a copy of the front end of the
database on their desktop. It would interact with the backend placed
somewhere on the server. This is a common setup. You would also have to
have access installed on the server. Access is a multi user RDMS therefore
no problems for more than one user.

FYI
 
Forgot to reply to the upload data issue. That is a bit more complicated.
I would probably
lean toward asp to do that. Terminal services does not natively offer a
file transfer process,
although there are server freeware add-on apps to do it. I guess it could
be done....
 
I am also available for hire.....

D said:
Oh jeez- I was afraid of that. Hmmmm... can you explain how the Terminal
Services deal works? Can an employee login from home, upload some files
from their machine locally to the Access virtual database, and then enter
data as well? How does that work if there's more than 1 person using the
database at the same time? That MIGHT be an option...

Thanks for the reply and links- I'll check those out as well. My problem is
my programmer doesnt know ASP and whatnot, soo... Im stuck using him, or,
fidning someone else for the job. I'm open to either, I just need this done
asap.
Thanks again!
D
Click to expand...
 
shar0n82 said:
Forgot to reply to the upload data issue. That is a bit more complicated.
I would probably
lean toward asp to do that. Terminal services does not natively offer a
file transfer process,
Click to expand...

Actually Server 2003 supports full redirection....
 
Before you go much further, I'd advise you to consider what server options
you have available.
If you're not using a Windows server, there will be extra costs in
supporting even ASP.
If you have a Windows server, but no Terminal Server, or no licenses, be
sure you factor those costs (and the time/costs of getting them set up) into
your project costs as you consider that alternative.

If your web hosting is a purchased service (you're not hosting this
in-house), you'll need to know what your provider can offer- and whether
that will change the price you're paying.

Without knowing these things, it would be difficult to make a decision on
whether to build a web-enabled front end for your tables/queries, or to use
an Access front-end over a Terminal Server.

BTW -
Whichever route you go, you can include as many queries as you like in
your back-end; they will be available just like the tables.
 
So let me get this right. Each 'employee' would have a copy of the front end
of the database on their own computers. Then, they do this Terminal Services
thing, tap into my server for the backend database. So, they have all their
forms and whatnot on the front end, sitting on their local machine, then,
the database itself, tables, etc will be sitting on the server. So, using
their front end forms/reports, they can tap into the backend (on the
server), access and modify records, export, import, create reports, etc
which will change on the backend.

Do I have this right?

How does the terminal services deal work? Is it just say, an IP address and
a password or something, and they login and now have access to it? Are
there any OS restrictions for the front end, or, will they all be able to
use the front end on XP, 2k, etc?

Last question- what do you charge per hour? Would you be up for creating a
system via ASP on teh web?
Thanks!
D
 
Going with the Terminal Service route- how fast/slow is this? How prone is
it to crashing? Is there a limit to a # of users at one time? Will it run
slow if there's 2-3 people working in it at one time from different
locations?
Thanks!
D
 
D said:
So let me get this right. Each 'employee' would have a copy of the front end
of the database on their own computers. Then, they do this Terminal Services
thing, tap into my server for the backend database. [Snip]
Click to expand...

Incorrect. Terminal Services lets the user "remotely" run programs on the
server. The ONLY program required on the client is the Terminal Server
client. However; each user running programs on the Terminal Server is
required to hold valid licenses for any software they run on the server in
addition to a Terminal Server license.
 
So let me get this right. Each 'employee' would have a copy of the front

Each 'employee' would have a copy of the front end of the
database in their profile (for example, in their documents
folder) on the server.

TS clients run on XP, 2K etc.

TS clients login to the server: normally you configure them
as normal windows users. They login, go to MyDocuments,
and open the database front end.
 
D said:
Going with the Terminal Service route- how fast/slow is this? How prone
is it to crashing? Is there a limit to a # of users at one time? Will it
run slow if there's 2-3 people working in it at one time from different
locations?
Thanks!
D
Click to expand...

TS is very reliable. And, no, it don't run slow with 2 or 5 remote people.
TS is a great solution for allowing your sales force, or people working at
home to use your application across the internet. If you are running windows
2000, or 2003 server, then TS is included. You can actually enable TS, and
then reboot the server..and you are up and running (I am not a network
guy..and this process is just a simple check box..and a re-boot). Once done,
you are allowed to have two free remote users at the same time. So, assuming
you will never have more then two remote users at the SAME TIME, then this
in effect is free for you to do this.

However, if you need MORE then 2 remote users at the same time, then you
have to start purchasing additional licenses to make this process happen.

Further, while it is a no brainier snap to enable TS, it certainly is NOT
EASY TO setup security correctly. In other words, if you are to expose your
server to the web, then you need very VERY competent server admin who know
how to do this. You likely would setup and use a Secure VPN to the server.

Also, TS is of course the same idea as remote desktop (in fact, it is based
on the same technology).

You can read about TS, and some other solutions to deploying ms-access to a
wide area network here:
http://www.attcanada.net/~kallal.msn/Wan/Wans.html
 
I don't have a SERVER running my Access app, just XP Pro that 3 users use
over a LAN. But I also need to let 1 other user have access to my app over
the internet. Terminal Services sounds like a GREAT quick solution.

So, can Terminal Services run on XP?

Tom
 
ThomasAJ said:
I don't have a SERVER running my Access app, just XP Pro that 3 users use
over a LAN. But I also need to let 1 other user have access to my app over
the internet. Terminal Services sounds like a GREAT quick solution.

So, can Terminal Services run on XP?
Click to expand...

Sort of!...you can run remote desktop, which is really a single user version
of TS.

TS is for server based systems. However, you can certainly enable remote
desktop on your windows xp box, and thus the person can use the computer
remotely. (remote desktop, and terminal services are the same thing. The
only real difference between TS and remote desktop is that TS creates
imaginary computers that people can connect to, and if you have 10 users
connecting to the one box, they ALL GET their own separate desktop. So, in
effect, TS kind of virtualizes windows, and can create a desktop for each
user that connects).

However, since you don't have a server, you can still use remote desktop,
and have the user connect to one computer (either the main box..or any other
computer in the office). So, remote desktop works exactly like TS..but only
allows one user to connect remotly. So, you can have that remote user
connect to, and use any computer in your office.
 
Note, however, that you can't use the host PC yourself at the same time that
someone else is using the Remote Desktop.
 
Back
Top