MS Access Key From Image

I wanted to share an additional option to my earlier blog regarding Sharepoint Attachments.  This design shows the flexibility that can be built into an MS Access Web Database.

Here it is:

In my web database (as described in my blog "MS Access SharePoint Attachment Field):

Add CLIENT forms that have an unbound Image Control, place TIF images in a consistent folder on the users computer (I would automate the daily image distribution).

Run my custom PopulateImages() function that adds the image names to a field in the table.

In the OnCurrent event of the form, set the unbound image control's "Picture" to the image.

As my tables are still Sharepoint lists, I still have the administrative advantages of a web database. This is more reasonable for higher daily volumes (remember it took and hour to add 150 images to the attachment field). It also gives the advantage of distributing any updates to users automatically whenever they login. Users can use the free MS Access 2010 runtime. Either browser based or client based can be available from the same application.

Private Sub Form_Current()
Dim MImage
MImage = "C:\folder\NewImages\" & Me.ImageName
Me.ImageNew.Picture = MImage
End Sub

What do you think?

Go Where the Work Takes You

I have been awarded several MS Access database development projects of late that I would like to share:

I recently completed an application for a wonderful European style bakery in Atlanta that is growing daily. The chef needed a way to control the process of receiving and tracking daily customer's orders, generating the baker's daily production reports with breakdown of dough types, dough volume required, and invoicing of customers. I worked closely with the client and we have developed a great tool that will make the daily process more efficient, easier to manage and less time consuming. Really enjoyed this project.

I am working on modifications to an application used by a local micro brewery to manage their process. This is a challenging project as I am wading through some very different, and totally without comments, code. To further complicate matters, the original programmer and I seem to approach the process differently. An occasional challenge can be good and keep you on your toes.

The third project is for an association that promotes a food product. Though I am modifying and adding to an existing application, I and the original programmer seem to approach the process similarly. I can more quickly understand where he is going.

The moral of the story is: Go where the work takes you. Be flexible enough to see a need and accept the challenge.