linking scanned field slips to forms

[datamanipulator]

I would like to reference scanned field slips and photographs in the forms I
have created- how is this best done?

 

[John W. Vinson]

I would like to reference scanned field slips and photographs in the forms I
have created- how is this best done?

More info please.

If you're trying to set up a database of images, your best bet would be to
store the images in one or more folders on disk, and create a Table with a
text field storing the path and filename of the image (together with other
appropriate identifying information). This table can be viewed on your form.

Do note that Forms are *decidedly secondary* - they do not store data, but are
just tools to manage data stored in Tables. If you're starting your database
design with the form, you're on the wrong track.

 

[datamanipulator]

No, I am not designing the db on the form- I just keep getting more field
data that need to be incorporated into a form so that they can be input into
the database-
Thank you for pointing this possibility out!

I do have a table set up with the fields slip data.
And at present have a txtbox on a form into which the field slipID is
entered- I need to be able to have actual slip come up on demand.

I have a bound object frame into which I would like the scanned field slip
to appear;
how to connect the txt box data with the correct OLE file?- something simple.

 

[GBA]

I like the hyperlink field; which is an optional field type property in Tables.

Once you get to know it; it works good.

Have a hyperlink field in the underlying table; and of course in your user
Form. When your cursor is this field - right click - then Edit Hyperlink -
and browse to your scanned document...once selected the hyperlink will then
appear in the field.

Then going forward - any time you click on it - it will launch that doc....

I've had alot of jobs where they needed a driver's license scanned in for
employees. And you don't want to pull that in everytime the form loads
because those scans are alot of bandwidth...and in fact users really don't
need to look at that license every time...so having that hyperlink field for
the drivers licenses allows them to look at it if they need to....its a good
pointer to the scanned doc.

hope this helps

 

[datamanipulator]

Thank you- this sound just the way to go.

I like the hyperlink field; which is an optional field type property in Tables.

Once you get to know it; it works good.

Have a hyperlink field in the underlying table; and of course in your user
Form. When your cursor is this field - right click - then Edit Hyperlink -
and browse to your scanned document...once selected the hyperlink will then
appear in the field.

Then going forward - any time you click on it - it will launch that doc....

I've had alot of jobs where they needed a driver's license scanned in for
employees. And you don't want to pull that in everytime the form loads
because those scans are alot of bandwidth...and in fact users really don't
need to look at that license every time...so having that hyperlink field for
the drivers licenses allows them to look at it if they need to....its a good
pointer to the scanned doc.

hope this helps

 

[John W. Vinson]

Thank you- this sound just the way to go.

Hyperlink is certainly a good option in this case. The only drawback is that a
Hyperlink field is a special case of a Memo field, and memo fields are at
somewhat more risk for corruption. I'm not aware of any special corruption
issues with hyperlinks though, so if it works for you go for it.

 

[datamanipulator]

John,
Given that not all the data is available through a hyperlink what
alternative could I use?

 

[John W. Vinson]

John,
Given that not all the data is available through a hyperlink what
alternative could I use?

I guess I don't understand. A hyperlink will point to an external file (say a
..jpg file if you're storing images), and open that file in some program
appropriate for that file type. What data is "not available"?

 

[datamanipulator]

John,
I suppose I am not fully understanding the hyperlink use-
Our data comes in as field slips- some pages of which have been scanned-
diagrams of cross-sections and the like-
these are what need to be linked to the forms- so that when the data for a
particular stn is needed in the future the slip can be pulled up.
At present I am creating the db for that field data- and had thought to use
the same feature on the form to enter the data into the associated tables.-
or am I putting the cart before the horse?

 

[John W. Vinson]

John,
I suppose I am not fully understanding the hyperlink use-
Our data comes in as field slips- some pages of which have been scanned-
diagrams of cross-sections and the like-
these are what need to be linked to the forms- so that when the data for a
particular stn is needed in the future the slip can be pulled up.
At present I am creating the db for that field data- and had thought to use
the same feature on the form to enter the data into the associated tables.-
or am I putting the cart before the horse?
"John W. Vinson" wrote:

A scanned image IS AN IMAGE. It's pixels on a page (or a screen). It is not
text and it cannot be directly entered into a table field, if that's what
you're talking about! You'll need to run the images through some sort of
optical character recognition software, correct the inevitable errors, and
then get the OCR'd data into your form. This is NOT a trivial task.

If you want to store *just the image* of the slip for humans to look at, then
you would probably have a table with a hyperlink field containing a link to
the image. If one project has multiple images you would have a projects table
related one to many to a table of images.

Are we on the same page now?