Best way to deal with a user's signature file and company logo
I am developing an Access 2010 database and have included a user's table. This table will be used to log on purposes but I also want to include the user's scanned signature file somehow and then use it on reports. So when the user runs a report I want their scanned signature to appear on the report.
How do I handle their signature in the user's table and then how do I make it appear on the report?
Also, I need to make their company logo show up on the report and I assume I can handle it the same way as the signature.
Thoughts?
How do I handle their signature in the user's table and then how do I make it appear on the report?
Also, I need to make their company logo show up on the report and I assume I can handle it the same way as the signature.
Thoughts?
ASKER CERTIFIED SOLUTION
membership
Create a free account to see this answer
Signing up is free and takes 30 seconds. No credit card required.
<Also, I need to make their company logo show up on the report and I assume I can handle it the same way as the signature.>
Clearly define what you mean by "Their"
Do each of "Them" have a separate logo?
What version of Access are you using?
If you need both a signature and an image associated with a Person (the mysterious "Them")
Then you can also "store" the images in an attachment field.
Linking vs Embedding an image is a tough call in a lot of circumstances, this is why you should always seek to give us as much info as possible:
Number of images
Size of the images,
Version of Access
...etc
Clearly define what you mean by "Their"
Do each of "Them" have a separate logo?
What version of Access are you using?
If you need both a signature and an image associated with a Person (the mysterious "Them")
Then you can also "store" the images in an attachment field.
Linking vs Embedding an image is a tough call in a lot of circumstances, this is why you should always seek to give us as much info as possible:
Number of images
Size of the images,
Version of Access
...etc
If you can use the Access 2007 format (.accdb) you can add a "Logo" and a "Signature" field to the Users table.
Make both datatypes: Attachment
Then use the built in interface (simply double-click the attachment field) to attach the image.
The great thing here is that simply dropping these image fields on the Form or Report, will make them display.
Like so:
Make both datatypes: Attachment
Then use the built in interface (simply double-click the attachment field) to attach the image.
The great thing here is that simply dropping these image fields on the Form or Report, will make them display.
Like so:
ASKER
I'm using Access 2010 so I can utilize attachments.
I want the signature file to be tied to the user's login. So I can include the signature field in the user's table.
The user then has the option of setting up a "Project" The logo file will be tied to the project. Strange I know but this is how it will work. So I'll tie the logo file to the project table.
I'm sorry if I don't always explain everything fully. I will try to do better.
I want the signature file to be tied to the user's login. So I can include the signature field in the user's table.
The user then has the option of setting up a "Project" The logo file will be tied to the project. Strange I know but this is how it will work. So I'll tie the logo file to the project table.
I'm sorry if I don't always explain everything fully. I will try to do better.
What is the system you are using to Log In?
Is the user Id Text or numeric?
...etc
(and once again.....
Post a sample database following these steps
(are you writing these steps down yet SteveL13...?)
1. Back up your database(s).
2. If the database is split, combine the front and back ends into one database file.
3. Remove any startup options, unless they are relevant to the issue.
4. Remove any extraneous records unless they are relevant to the issue.
5. Delete any objects that do not relate directly to the issue.
6. Remove any references to any "linked" files (files outside of the database, Images, OLE Files, ...etc)
7. Remove any references to any third party Active-x Controls (unless they are relevant to the issue)
8. Remove, obfuscate, encrypt, or otherwise disguise, any sensitive data.
9. Unhide any hidden database objects
10. Compile the code. (From the VBA code window, click: Debug-->Compile)
11. Run the Compact/Repair utility.
12. Remove any Passwords, Security and/or login prompts.
13. If a form is involved in the issue, set the Modal and Popup properties to: No
(Again, unless these properties are associated with the issue)
14. Post the explicit steps to replicate the issue.
15. Test the database before posting.
In other words, ...post a database that we can easily open and immediately see and/or troubleshoot the issue.
And if applicable, also include a clear, graphical representation of the *Exact* results you are expecting, based on the sample data.
In a nutshell...
You will store the UserID (as a Public Variable) when they log in.
In a module do something like this:
Public lngpubUID as Long
In your Login code, do something like this:
lngpubUID =[The Users Login ID]
...Then you can use a Public function to retrieve this value:
Public Function GetUID as long
GetUID =lngpubUID
End function
... and use it as a filter for all their forms/Reports
something like this:
DoCmd.OpenForm "YourForm", , , "UserID=" & GetUID ()
< The logo file will be tied to the project. >
This was not clear from your original post.
So get the log in stuff going first... perhaps the Logo-Project link issue will be better answered if posted as a separate question...
JeffCoachman
Is the user Id Text or numeric?
...etc
(and once again.....
Post a sample database following these steps
(are you writing these steps down yet SteveL13...?)
1. Back up your database(s).
2. If the database is split, combine the front and back ends into one database file.
3. Remove any startup options, unless they are relevant to the issue.
4. Remove any extraneous records unless they are relevant to the issue.
5. Delete any objects that do not relate directly to the issue.
6. Remove any references to any "linked" files (files outside of the database, Images, OLE Files, ...etc)
7. Remove any references to any third party Active-x Controls (unless they are relevant to the issue)
8. Remove, obfuscate, encrypt, or otherwise disguise, any sensitive data.
9. Unhide any hidden database objects
10. Compile the code. (From the VBA code window, click: Debug-->Compile)
11. Run the Compact/Repair utility.
12. Remove any Passwords, Security and/or login prompts.
13. If a form is involved in the issue, set the Modal and Popup properties to: No
(Again, unless these properties are associated with the issue)
14. Post the explicit steps to replicate the issue.
15. Test the database before posting.
In other words, ...post a database that we can easily open and immediately see and/or troubleshoot the issue.
And if applicable, also include a clear, graphical representation of the *Exact* results you are expecting, based on the sample data.
In a nutshell...
You will store the UserID (as a Public Variable) when they log in.
In a module do something like this:
Public lngpubUID as Long
In your Login code, do something like this:
lngpubUID =[The Users Login ID]
...Then you can use a Public function to retrieve this value:
Public Function GetUID as long
GetUID =lngpubUID
End function
... and use it as a filter for all their forms/Reports
something like this:
DoCmd.OpenForm "YourForm", , , "UserID=" & GetUID ()
< The logo file will be tied to the project. >
This was not clear from your original post.
So get the log in stuff going first... perhaps the Logo-Project link issue will be better answered if posted as a separate question...
JeffCoachman
Example: Picture in a Report