|
Welcome to Personal Computer Consultants where we provide
you with custom solutions to those tasks that eat up all of your valuable
time.
Microsoft Access database development and creating some
handy tools, is a skill I have developed over the years ever since it was
introduced. Some people call me a
guru. Being familiar with various
aspects of the different versions of Windows and setting up my own servers
and network, I have gotten a reputation as the goto
guy when things aren’t working.
Are you reaching the 2 gigabyte limit of Microsoft
Access? If so then you have more
data than Microsoft Access can handle. What do you do? Well the easy
solution is to move all your data to Microsoft SQL Server and modify your
Microsoft Access front-end to use SQL Server tables. Doing this speeds up your database if
you do it right. The difference in
speed is remarkable to say the least.
Yes, you need skills for developing SQL Server Databases and I have taken
existing queries and used my little tool to automatically create Stored
Procedures.
Many of the solutions that I have worked on required
knowledge and experience with several systems, web sites, xml, c#, and
various Microsoft products. While
I am no expert at any of these, I did my research, found out just what I
needed to know and used these technologies in a solution that saved many
valuable hours for my clients.
You can imagine a manager who needs to figure out a solution
to his data management problem and the IT department offers support but
no real solutions. Is this you?
Many managers do not understand how quickly a solution can
be implemented because IT has told them that setting up a SQL Server
database is a long and drawn out process.
I can simplify that process!
I will do all the work.
As an example, a recent client needed to re-run 350 queries
in a Microsoft Access database every quarter for risk assessment
purposes. The problem was that
several of their linked tables were in Microsoft Access databases that
were at the 2 gigabyte limit and had to do something quickly before they
blew up (and always without warning when they do).
My first task was to move all the data to a new SQL server
database (2008 R2), which I created on my local machine. Then I created a
stored procedure for each of the 350 queries so that all the processing
would be done on the SQL server and not in Microsoft Access. I actually
created a little utility in Microsoft Access to create the Stored
Procedures automatically. Cool.
Then I created a user interface in a Microsoft Access
database to run each stored procedure and capture any errors that may occur. Once testing was completed I moved the
entire SQL server database to a production server without any help from
IT. This process ran all the
stored procedures from Microsoft Access VBA code, captured errors if any,
and logged them for later review.
I required only minimal support from IT as I have set up my
own networks, servers, routers, switches.
I built my own patch panels to switch between different computers
quickly and have built my own computers in the past. I have experience in a wide area of
knowledge. Although databases are
my specialty.
This process was run on a quarterly basis and usually took
the client over two weeks to run all of the queries. The new process was better and easier
to manage and took only 45 minutes to run! Yes, a savings of two weeks processing!
This could be you! Is
your Microsoft Access database a problem?
Let’s fix it!
Let me put your problem and my solutions together and you
will save lots of time and effort with better solutions that are
scalable.
|
