Tom - Access can easily handle this.

When you create the database, the simplest method would be to make the job #
field the key field and make it a counter type field so it automatically
increments itself each time you add a new record.  If you want to write some
code, you could add the year and/or month to the job # field but you get
this same info from the date field so this complexity is probably not
needed.

When you create the field for the image, make the data type an OLE Object.
Create a form to enter data and tweak the size of the window to display the
images.  This allows you to paste the image into the record by copying the
image and hitting Ctrl-V in the image field on the form.

As the application grows, you may split the customer names into a separate
table etc.  For now, something this simple can be handled in one table in
Access.

Hth,
Steve M.

        I need to create a database that will contain the following
information:
        Job #
        Customer Name
        Job Date
        Scanned images of job tickets (could be as many as 10 scanned 8 1/2
x 11
        pages per job)

        The users need to be able to do a lookup based on customer name, a
range of
        job numbers or a range of dates and view the scanned images as
appropriate.

        The user currently has MS Access.  Is this a good choice for this
type of
        database?

        Thanks
        Tom Cassidy

                Curious about the people moderating your
                   messages? Visit our staff web site:
                     http://nospin.com/pc/staff.html