Search results

Got it! Thanks to all who answered. I eventually went with the solution proposed by theDBguy, but IslaDogs' code did tell me I was going in the right direction (steps outlined below, in case it helps anyone else). I feel a little stupid for not thinking of it myself, but that's the benefit of...

With a form, I've used search and replace e.g. strSearch = RstKey!keyword strNew = "<b><font color=red size = 4>" & strSearch & "</font></b>" Forms!frmPDResults!txtSynopsis = Replace(Forms!frmPDResults!txtSynopsis, strSearch, strNew) With the report, this same method produces an error telling...

Just to clarify, the report is opened in design view as the source is being reset. I left it in that view because I thought it needed to be, to do the rest of the manipulation, but I can close it and open it in preview mode if required.

I'm just playing with that at the moment. Fiddly, but I think I see how it could work (and I'll take fiddly over not working).

That would work perfectly! I'm changing font colour but highlighting would do the job just as well. The same colour for each word would be fine (I think some of the users might be put off by too many colours).

Sorry, that was just a sub procedure that's being called to do the highlighting, the report is already open in design view at that point.

No. If I ask you not to give a medical opinion on something because you're not qualified, that doesn't mean I'm giving a medical opinion. The same goes for a political opinion.

I found the following online and after a couple of tweaks it works well to highlight each instance of a single word in the 'Synopsis' field of a report. Sub Highlight_Keywords() Dim RstKey As Recordset Dim strSearch As String Dim strTemp As String Dim strTempEnd As String...

Thanks, will do. If so, it would have been many years back. I started using an alias after I got some abusive private messages. I'll take you up on this, I think. I need to keep on it, but no need to keep it open on here. I will delete the attachments from the posts.

Yes. The problem is reproducable in the standalone version I uploaded. It's on my C drive. No other users or databases are involved. No connections are involved. In the live version, there is a separate front and back end but the problem is the same in this standalone version, which is entirely...

The reason for the multiple 'set' locations was for testing, by my predecessor. If he wanted to only open a particular form and test it, thereby bypassing ModelWarranty, the variable db wouldn't get set. By putting it at other points in the code, he got past this. I'll change the code to make...

Please don't spend any more time on this. Db is declared as a global variable in module 'modPubRoutines' and was initially set to CurrentDb when in the FormOpen event of ModelWarranty. When I deleted the code that hid the toolbar and stopped the close button working, I inadvertently took out...

Okay, not trying to be difficult but it seems I have been. I genuinely appreciate the help certain people have offered. New version of the db attached. Timer disabled, all menus and close button visible. Instructions for how I recreate the problem (including relevant form names) as follows: 1...

Sorry, I'm not sure where the confusion is coming in? Ignore the tab controls. The tab controls aren't relevant, just use the buttons named. I've attached a document with pictures of each stage up to 7.

Thanks for the comments. I don't expect you to waste any time on this. I converted all tables to local versions but forgot to remove the call to connect to them. Now done. I didn't disable the button. It stops working for some reason when another occurs. I've just gone in and out a few times...

Good to hear, what with?

Okay, I created a very cut down version with gibberish data, so I could upload it. Ignore any errors outside those generated by the following steps. The steps to recreate the problem: 1. I open the db 2. Alt + F11 and make any change to the code. No problems. 3. Click on <Show Toolbar> 4. Alt...

Just tried it, same result for that user.

Was halfway through typing the same thing. :)

Nice idea, but the company replaces our laptops every year, so the one I'm using now is different from the one the db was built on and the one where I found the initial problem.:( Hopefully, once I've made a cut down version, one of the big brains here will spot something that dullards like me miss.