Access on the web

[Guest]

Hi all

This may not be the best forum to post this but thought I'd try it since you
all use Access and are developers ;-).

I have developed in Access for quite a few years and can do basic coding and
some more advanced stuff with the help of you guys! We currently send
transfer files (small access db's) backwards and forwards from the office to
our field staff. The company I work for want to make the data available on
the web:
a) for customers to download
b) to enable field staff to be able to add/edit live data
c) Create recordsets to download (claim files)

We also want to host our own web site and create a basic web based CRM system.

Can anyone offer any advice on the way forward? I was told sql server and
vb.net (or asp.net) but other people say ASP and Access purely because it
would be quicker and easier for me to achieve. But isn't ASP redundant/old
software? I don't want to invest time and money learning something which is
being phased out.

Thanks for any advice.
Sue

 

[MikeR]

Hi all

This may not be the best forum to post this but thought I'd try it since you
all use Access and are developers ;-).

I have developed in Access for quite a few years and can do basic coding and
some more advanced stuff with the help of you guys! We currently send
transfer files (small access db's) backwards and forwards from the office to
our field staff. The company I work for want to make the data available on
the web:
a) for customers to download
b) to enable field staff to be able to add/edit live data
c) Create recordsets to download (claim files)

We also want to host our own web site and create a basic web based CRM system.

Can anyone offer any advice on the way forward? I was told sql server and
vb.net (or asp.net) but other people say ASP and Access purely because it
would be quicker and easier for me to achieve. But isn't ASP redundant/old
software? I don't want to invest time and money learning something which is
being phased out.

Thanks for any advice.
Sue

Classic ASP will be around for a long time, I think. It would be the easiest
solution currently available (coding is closer to what you already know), unless
you already have a .NET developer in-house. The learning curve there is a bit
steeper than classic ASP. BTW, you can use SQLServer with ASP if your database
needs are greater than what Access can provide, but it doesn't seem so from your
post. Take a look in microsoft.public.inetserver.asp.db , and m.p.i.asp.general.
There are a lot of tutorials on the web, so Google away.
Have fun!
Mike

 

[Guest]

Thanks Mike for your advice. Access works well currently, the only thoughts I
have had is that SQL server may be more secure over the web and possibly run
quicker? I may convert the tables but keep the front-end in Access for the
office use. I do not know HTML either but I am hoping to get some training
paid for by work which will be a novelty for me as I've always been self
taught.

Sue