History: I work for the IT/MIS in the Public Sector. The company has recently moved from using Oracle on Unix to SQL Server 2000, due to lack of technical support for Unix.
My job is to develop end-user mdbs/adps that will cater for the least experienced user, who will access information through automated forms; and for users (who are experienced Oracle users) who will be either updating the data or writing their own SQL Queries. The information we process comes in a very raw format from outside the company, for eg, csv files, requiring: data cleaning, updating etc.
Problem1: I need to sell the virtues of using an adp file as an end tool, to my Oracle using Information Section, for updating and maintaining their data tables held on the SQL Server.
Problem2: Converting a database which came to me in mdb format with csv data files. I have loaded the data files on the Server, no problem. The mdb also has a phenomenal amount of select queries. Again I need to sell the virtues of putting any standard queries onto the SQL Server side and connect to them using a Pass-Through query. Rather than linking tables to the mdb file. This database has approx. 0.5 million records.
Problem3: I am the only person within the IT section, who has a working knowledge Visual Basic, again because the company has been using Oracle on Unix, the concept of automated forms is an anathema. Again, I need to sell the virtues of a user friendly front-end tool that will enable ease of access to information.
I could go on. The people I need to convince on SQL Server, ADP -v- MDB, aren't particularly technically minded. They've used Oracle on Unix for quite sometime, have little knowledge of Access mdb, nor the time involved to develop a flexible system.
This is a bit of a mixed bag, but any advice would be very helpful.