I have a very large messed up client 
They have an extensive intranet network with several oracle / legacy unix etc based data warehouses. They have been developing mini-apps in MS-ACCESS and Excel/VBA to pull via ODBC info and manipulate it.
The mini-apps have become so numerous that there is little control and consolidation of anything.
I am tasked with trying to help solve this problem. That is where I need some advice, because I'm not an guru in SQL or web-gineering.
Requirements:
1. I'm looking to move to a SQL server back end - that will act as a go between from the Oracle / legacy Data warehouses. This way I can make changes in something familiar (I know SQL well but not exactly a SQL server admin expert). And also once the SQL server is implemented I will be able to teach how to use it. I've been using SQL server 2000 alot, but I have only installed it for small clients (free version), and locally. I will have to gain permission to put SQL on the intranet etc.. was looking at 2005 version.
2. I need a unified Front end - User interface. Currently I've been writing in pure VB 6, MS-ACCESS 2000 - 02, some ASP, a little ASP.NET, a LITTLE Java, and bit this and that. I want to really lock down the user interface within IE - Browser window. What I'd like some advice on - there are so many GUI's to choose from. I just need something:
A> Easy to learn - simple so I can teach it, but powerful enough to have the power to do whatever I need done without a significant learning curve - IE. I don't want to learn Fortran.
B> It will be almost 100% INTRANET web based. But the applications will be like mini-ACCESS forms. So the functionality needs to be extensive MS-ACCESS like (activeX).
C> ODBC and easy to bring in data from Back End
D> 15 - 20 users on at once (this is the HIGH END) It will more likely be 5 - 10.
E> The possibility in the future to push some stuff out to a INTERNET or at least develop portions that will be inter-connected Internet to Intranet - IE. Sales forces in the field can log in and enter info and HQ can read it.
F> Extensive Reports / matrix (datagrid / comparisons of data/ trend analysis)
Any advice would be GREATLY appreciated. I'm considering all solutions - and don't want to just go with what I know.. I'd much rather look at a solution that brings in short term results right now for the client, and also has longevity where I don't have to worry about limitations in the future.
Your past experience with back end to front end development is key here.
Thanks Tek-Tips community.
- L
They have an extensive intranet network with several oracle / legacy unix etc based data warehouses. They have been developing mini-apps in MS-ACCESS and Excel/VBA to pull via ODBC info and manipulate it.
The mini-apps have become so numerous that there is little control and consolidation of anything.
I am tasked with trying to help solve this problem. That is where I need some advice, because I'm not an guru in SQL or web-gineering.
Requirements:
1. I'm looking to move to a SQL server back end - that will act as a go between from the Oracle / legacy Data warehouses. This way I can make changes in something familiar (I know SQL well but not exactly a SQL server admin expert). And also once the SQL server is implemented I will be able to teach how to use it. I've been using SQL server 2000 alot, but I have only installed it for small clients (free version), and locally. I will have to gain permission to put SQL on the intranet etc.. was looking at 2005 version.
2. I need a unified Front end - User interface. Currently I've been writing in pure VB 6, MS-ACCESS 2000 - 02, some ASP, a little ASP.NET, a LITTLE Java, and bit this and that. I want to really lock down the user interface within IE - Browser window. What I'd like some advice on - there are so many GUI's to choose from. I just need something:
A> Easy to learn - simple so I can teach it, but powerful enough to have the power to do whatever I need done without a significant learning curve - IE. I don't want to learn Fortran.
B> It will be almost 100% INTRANET web based. But the applications will be like mini-ACCESS forms. So the functionality needs to be extensive MS-ACCESS like (activeX).
C> ODBC and easy to bring in data from Back End
D> 15 - 20 users on at once (this is the HIGH END) It will more likely be 5 - 10.
E> The possibility in the future to push some stuff out to a INTERNET or at least develop portions that will be inter-connected Internet to Intranet - IE. Sales forces in the field can log in and enter info and HQ can read it.
F> Extensive Reports / matrix (datagrid / comparisons of data/ trend analysis)
Any advice would be GREATLY appreciated. I'm considering all solutions - and don't want to just go with what I know.. I'd much rather look at a solution that brings in short term results right now for the client, and also has longevity where I don't have to worry about limitations in the future.
Your past experience with back end to front end development is key here.
Thanks Tek-Tips community.
- L