Application w/Access Backend

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I need to put together an application with an access 2003 backend database
but unsure on the front end. We have used MS Access for front end but it's
not as clean an interface as I would like. Can you suggest what I might use
and possible resources to get up and running on it?

Thanks!
 
I need to put together an application with an
access 2003 backend database but unsure on
the front end. We have used MS Access for
front end but it's not as clean an interface as I
would like. Can you suggest what I might use
and possible resources to get up and running
on it?
Click to expand...

I've used Microsoft Access as a user interface since 1993, and wonder just
what you mean by "not as clean an interface as I would like."

If you can clarify, with details, perhaps someone can assist you in
improving the Access interface, or suggesting some other development tools.

Larry Linson
 
Well, you can write a widows batch file (script) to open, and read a mdb
file!!!.

So, virtually any development tool that supports com objects should work for
you.....

Delphi, VB, VB.net, c#, c++....all of them can work with, and use a mdb
(jet) file format.

As for clean interface, take a look at at the following:

http://www.members.shaw.ca/AlbertKallal/Articles/Grid.htm

I will admit that the interface you build can be clean, clutter free, and
generally quite nice. I think when you start to build a REAL rich interface
with all kinds of widgets etc, then that is the time were ms-access might
not be the right tool....

The above will give you some ideas. Here is some additional screen shots of
ms-access applications:

http://www.members.shaw.ca/AlbertKallal/Articles/UseAbility/UserFriendly.htm

None of the above screens use any special tricks, and are all standard
ms-access controls and screens.

You might want to expand on what kind of interface you are looking towards.
When you keep things clean and straight forward, I think ms-access is a
great tool.

Here is more screen sequences for another application of mine. Again, they
might give you some ideas...

http://www.kallal.ca/ridestutorialp/index.html
 
Don't get me wrong - I love MS Access. What I am looking for is a bit more
polish and I was thinking that maybe VB could provide that polish. However,
if someone would be willing to spend a bit of time to look over a three
screen shots and provide a few critical comments and offer suggestions on
making improvements then that would be great. Is someone interested? You
can contact me directly at (e-mail address removed)

Thanks!
 
NC Beach Bum said:
Don't get me wrong - I love MS Access. What I am looking for is a bit
more
polish and I was thinking that maybe VB could provide that polish.
However,
if someone would be willing to spend a bit of time to look over a three
screen shots and provide a few critical comments and offer suggestions on
making improvements then that would be great. Is someone interested?
You
can contact me directly at (e-mail address removed)
Click to expand...

Oh, maybe you mean what my clients would call "glitz and glitter". My
clients want Access to address business problems, but none of them wants to
spend a nanocent on "glitz and glitter."

My experience with VB was with "classic VB" which did give you "closer
control over the UI" and for which there were uncounted numbers of
third-party ActiveX Controls that you could purchase. What else it entailed
was at least three times the time and effort to implement identical
applications, and high costs if you opted to get third-part ActiveX
Controls... some of which you'd need just to match the built-in controls in
Access.

VB.NET also has extra capabilities in this area. My observation is that it
has a significant learning curve, and that third-party Controls are usually
even more expensive than their classic VB counterparts. Some who are more
knowledgeable about it than I am expect that the next release, or perhaps
the one after that, may live up to the original promises for
easy-to-develop, easy-to-use Windows applications, but think that now it is
primarily useful for web-based applications. There is _not_, however, as far
as I know, _conversion software_ to convert an Access application to a
VB.NET application, so you should expect to re-create the application, but
likely be able to use the database that you already have.

Larry Linson
Microsoft Access MVP
 
Gotcha - then I will stay with Access and look to add some spit and polish to
the application. Can you suggest a good book that might help me?
 
Gotcha - then I will stay with Access and look
to add some spit and polish to the application.
Can you suggest a good book that might help me?
Click to expand...

Rebecca Riordan wrote a book on the subject, and I find her books helpful --
however, I believe her UI book was in the context of DotNet applications.
(Sorry, I am away from my normal 'base of operations' so can't grab it and
give the publisher and ISBN.) Microsoft Press has published books on
recommended UI practices -- and some of the recommendations change over
time. A well-known book is "About Face" by Alan Cooper, original writer of
the base code from which Microsoft developed classic VB.

My personal recommendations: make it clean and simple -- don't overwhelm the
user with information on one screen and don't put anything distracting on
the screen... like a traffic light that cycles through its colors, etc. One
of my personal pet peeves is Controls that fade-in and fade-out... almost
always the implementer's ego trip makes me wait to enter my data into the
application or website. Make certain there's good contrast between the text
and the background, and make the text big enough that even eyeglasses
wearers who took their glasses off to rest their eyes can read it (even if
they have to lean in close). Even 10 point text can be hard to read, on a
high-res screen.

Larry Linson
Microsoft Access MVP
 
Back
Top