By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
443,310 Members | 1,430 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 443,310 IT Pros & Developers. It's quick & easy.

Which db and front end do we go

P: n/a
We have been developing in MS Access/VBA for nearly 10 years now and find we
need to get with the times and look at a web type of front end to a more
robust/multi user back end.

I would be interested to here any thoughts on which way we should go. We
currently have an IT Help Desk application that we need to duplicate in new
technology (example at http:jackaroo.net.au) which needs to be able to have
many users eg Corp wide and to handle say 50,000 records. Cost to the client
is a main concern hence why we used Access but we are now thinking possibly
MySQL or ????? (any thoughts) and say a HTML front end created with
Macromedia Flash or ?????? (any thoughts).

Thanks for your thoughts.

--
Regards
Ian Baker
Jackaroo Developments Pty Ltd
(Download Jackaroo IT - IT Mgmt and Help Desk application at
http://jackaroo.net.au)
Jul 19 '05 #1
Share this Question
Share on Google+
6 Replies


P: n/a
I too came from the Access/VBA world and changed quite happily to Web based,
mysql based world.

Here's what I'd do. I'm Linux savvy but basic plan should also work on
Windows.

Load Linux on a box (an old slow one is ok say 200+mhz, 64+ram)
Install PHP4, MySQL, Apache (language, sql, webserver)
Access databases can export to Mysql via ODBC (a separate step).
Then write PHP4 code, running from the Web server, and accessing MySql.
The queries against 50K records should be a piece of cake for
Linux/Mysql/PHP.

That's my initial thoughts with no more details then this to start.
dp
"Ian Baker" <ia*@REMOVE-CAPITALS-FOR-EMAILjackaroo.net.au> wrote in message
news:3f**********************@news.optusnet.com.au ...
We have been developing in MS Access/VBA for nearly 10 years now and find we need to get with the times and look at a web type of front end to a more
robust/multi user back end.

I would be interested to here any thoughts on which way we should go. We
currently have an IT Help Desk application that we need to duplicate in new technology (example at http:jackaroo.net.au) which needs to be able to have many users eg Corp wide and to handle say 50,000 records. Cost to the client is a main concern hence why we used Access but we are now thinking possibly MySQL or ????? (any thoughts) and say a HTML front end created with
Macromedia Flash or ?????? (any thoughts).

Thanks for your thoughts.

--
Regards
Ian Baker
Jackaroo Developments Pty Ltd
(Download Jackaroo IT - IT Mgmt and Help Desk application at
http://jackaroo.net.au)

Jul 19 '05 #2

P: n/a
I too came from the Access/VBA world and changed quite happily to Web based,
mysql based world.

Here's what I'd do. I'm Linux savvy but basic plan should also work on
Windows.

Load Linux on a box (an old slow one is ok say 200+mhz, 64+ram)
Install PHP4, MySQL, Apache (language, sql, webserver)
Access databases can export to Mysql via ODBC (a separate step).
Then write PHP4 code, running from the Web server, and accessing MySql.
The queries against 50K records should be a piece of cake for
Linux/Mysql/PHP.

That's my initial thoughts with no more details then this to start.
dp
"Ian Baker" <ia*@REMOVE-CAPITALS-FOR-EMAILjackaroo.net.au> wrote in message
news:3f**********************@news.optusnet.com.au ...
We have been developing in MS Access/VBA for nearly 10 years now and find we need to get with the times and look at a web type of front end to a more
robust/multi user back end.

I would be interested to here any thoughts on which way we should go. We
currently have an IT Help Desk application that we need to duplicate in new technology (example at http:jackaroo.net.au) which needs to be able to have many users eg Corp wide and to handle say 50,000 records. Cost to the client is a main concern hence why we used Access but we are now thinking possibly MySQL or ????? (any thoughts) and say a HTML front end created with
Macromedia Flash or ?????? (any thoughts).

Thanks for your thoughts.

--
Regards
Ian Baker
Jackaroo Developments Pty Ltd
(Download Jackaroo IT - IT Mgmt and Help Desk application at
http://jackaroo.net.au)

Jul 19 '05 #3

P: n/a
D. Pickering
Thanks for your input. I have spent the last couple of days looking into all
of this and I believe the way for us to go with our Help Desk app is ASP.NET
using VBScript as the front end and for now stay with Jet as the backend
simply because it is free (via MSOffice Developer). Once we have got our
heads around the learning curve for the front end which I feel will take a
year or so to develop a robust and proven app we will probably look at MySQL
as the backend. SQLServer would be far to costly for our clients (50 to 250
employee sized organisations) and MSDE wouldn't work as there will probably
be up to 10 normal help desk people as concurrent users and with a light
version on all employees desktops accessing the db to log/view their own
help desk calls the strain will probably be to much

Does this sound fair and reasonable to you?

Thanks again

--
Regards
Ian Baker
Jackaroo Developments Pty Ltd
(Download Jackaroo IT - IT Mgmt and Help Desk application at
http://jackaroo.net.au)
"D. Pickering" <dc*****@hps.com> wrote in message
news:w8*********************@newssvr30.news.prodig y.com...
I too came from the Access/VBA world and changed quite happily to Web based, mysql based world.

Here's what I'd do. I'm Linux savvy but basic plan should also work on
Windows.

Load Linux on a box (an old slow one is ok say 200+mhz, 64+ram)
Install PHP4, MySQL, Apache (language, sql, webserver)
Access databases can export to Mysql via ODBC (a separate step).
Then write PHP4 code, running from the Web server, and accessing MySql.
The queries against 50K records should be a piece of cake for
Linux/Mysql/PHP.

That's my initial thoughts with no more details then this to start.
dp
"Ian Baker" <ia*@REMOVE-CAPITALS-FOR-EMAILjackaroo.net.au> wrote in message news:3f**********************@news.optusnet.com.au ...
We have been developing in MS Access/VBA for nearly 10 years now and
find we
need to get with the times and look at a web type of front end to a more
robust/multi user back end.

I would be interested to here any thoughts on which way we should go. We
currently have an IT Help Desk application that we need to duplicate in

new
technology (example at http:jackaroo.net.au) which needs to be able to

have
many users eg Corp wide and to handle say 50,000 records. Cost to the

client
is a main concern hence why we used Access but we are now thinking

possibly
MySQL or ????? (any thoughts) and say a HTML front end created with
Macromedia Flash or ?????? (any thoughts).

Thanks for your thoughts.

--
Regards
Ian Baker
Jackaroo Developments Pty Ltd
(Download Jackaroo IT - IT Mgmt and Help Desk application at
http://jackaroo.net.au)


Jul 19 '05 #4

P: n/a
D. Pickering
Thanks for your input. I have spent the last couple of days looking into all
of this and I believe the way for us to go with our Help Desk app is ASP.NET
using VBScript as the front end and for now stay with Jet as the backend
simply because it is free (via MSOffice Developer). Once we have got our
heads around the learning curve for the front end which I feel will take a
year or so to develop a robust and proven app we will probably look at MySQL
as the backend. SQLServer would be far to costly for our clients (50 to 250
employee sized organisations) and MSDE wouldn't work as there will probably
be up to 10 normal help desk people as concurrent users and with a light
version on all employees desktops accessing the db to log/view their own
help desk calls the strain will probably be to much

Does this sound fair and reasonable to you?

Thanks again

--
Regards
Ian Baker
Jackaroo Developments Pty Ltd
(Download Jackaroo IT - IT Mgmt and Help Desk application at
http://jackaroo.net.au)
"D. Pickering" <dc*****@hps.com> wrote in message
news:w8*********************@newssvr30.news.prodig y.com...
I too came from the Access/VBA world and changed quite happily to Web based, mysql based world.

Here's what I'd do. I'm Linux savvy but basic plan should also work on
Windows.

Load Linux on a box (an old slow one is ok say 200+mhz, 64+ram)
Install PHP4, MySQL, Apache (language, sql, webserver)
Access databases can export to Mysql via ODBC (a separate step).
Then write PHP4 code, running from the Web server, and accessing MySql.
The queries against 50K records should be a piece of cake for
Linux/Mysql/PHP.

That's my initial thoughts with no more details then this to start.
dp
"Ian Baker" <ia*@REMOVE-CAPITALS-FOR-EMAILjackaroo.net.au> wrote in message news:3f**********************@news.optusnet.com.au ...
We have been developing in MS Access/VBA for nearly 10 years now and
find we
need to get with the times and look at a web type of front end to a more
robust/multi user back end.

I would be interested to here any thoughts on which way we should go. We
currently have an IT Help Desk application that we need to duplicate in

new
technology (example at http:jackaroo.net.au) which needs to be able to

have
many users eg Corp wide and to handle say 50,000 records. Cost to the

client
is a main concern hence why we used Access but we are now thinking

possibly
MySQL or ????? (any thoughts) and say a HTML front end created with
Macromedia Flash or ?????? (any thoughts).

Thanks for your thoughts.

--
Regards
Ian Baker
Jackaroo Developments Pty Ltd
(Download Jackaroo IT - IT Mgmt and Help Desk application at
http://jackaroo.net.au)


Jul 19 '05 #5

P: n/a
"Ian Baker" <ia*@REMOVE-CAPITALS-FOR-EMAILjackaroo.net.au> wrote in message
news:3f***********************@news.optusnet.com.a u...
D. Pickering
Thanks for your input. I have spent the last couple of days looking into all of this and I believe the way for us to go with our Help Desk app is ASP.NET using VBScript as the front end and for now stay with Jet as the backend
simply because it is free (via MSOffice Developer). Once we have got our
heads around the learning curve for the front end which I feel will take a
year or so to develop a robust and proven app we will probably look at MySQL as the backend....


If you're going through the redevelopment process, I'd suggest going ahead
and do the jump to the new backend at the same time. As there are SQL-syntax
differences, field type differences, etc, the front-end will need some
coding and testing specific to the database backend, and so to me it makes
sense to re-code and test both ends at the same time.

Ray Gurganus
www.citidc.com
Jul 19 '05 #6

P: n/a
"Ian Baker" <ia*@REMOVE-CAPITALS-FOR-EMAILjackaroo.net.au> wrote in message
news:3f***********************@news.optusnet.com.a u...
D. Pickering
Thanks for your input. I have spent the last couple of days looking into all of this and I believe the way for us to go with our Help Desk app is ASP.NET using VBScript as the front end and for now stay with Jet as the backend
simply because it is free (via MSOffice Developer). Once we have got our
heads around the learning curve for the front end which I feel will take a
year or so to develop a robust and proven app we will probably look at MySQL as the backend....


If you're going through the redevelopment process, I'd suggest going ahead
and do the jump to the new backend at the same time. As there are SQL-syntax
differences, field type differences, etc, the front-end will need some
coding and testing specific to the database backend, and so to me it makes
sense to re-code and test both ends at the same time.

Ray Gurganus
www.citidc.com
Jul 19 '05 #7

This discussion thread is closed

Replies have been disabled for this discussion.