Identify Highlighted or Bolded cells with code

[usa_dreamer2002]

Hi all,
this is a weird question. I receive a bunch of excel files with items to be added to a database. some of the items are to be added as new, some to be deleted and others to be modified.
I identify the action (add/delete/modify) by looking at a column in the excel file e.g. column A.
at this point I am fine with the add/delete because I can filter the data or bring all the files to a temporary table in an Access database via vba script and then running queries to do the rest.

My issue is that the spreadsheets have a lot of columns and for the modifications what they do is use the same file for instance, make changes on the cells (any cell) that need modification and then highlight, bold or underline only the items that need modification and ignore the rest of the file (a tedious process since I have to then open each file and manually modify the database). Can anyone advise of any way (or tool) that could be used to accomplish the modification task?
I would post the same in the MS Access Forum as I could use help either in Access or Excel.

Thank you in advance.
​

 

[Rx_]

This is a constant question where people try to link Excel to an Access table.
There are several considerations that revolve around design and code.
Excel is something I personally love. But, from a user standpoint, it is typically anarchy from a user's perspective when it comes to data.
By creating templates in Excel, it can be somewhat tamed.

To answer your question, it takes code, a lot of custom code, to bind the two together. This includes code to look at the formatting in Excel and decide what to do with it in Access (and vice versa).

There are excellent demos and code on this site about moving Access into formatted Excel. However the DoCmd is just a generic quick method. Your example will require building recordsets and using Excel Object Model code.
By building reports from Access in Excel, the template is put into place.
I often hide columns with Primary Keys so that users can update the Excel. Then use the hidden primary keys to pull the Excel back and look for modifications.
This way, the data of record is always in Access tables.

There is no single script to use. It requires workflow management in a plan so that custom code can be built.

So, you found a good site. My advice is to come up with a plan then break down each step that to accomplish the task.
Depending on your skill level, http://www.btabdevelopment.com/ts/ might be a good place to start.