Search results

Of course it's best to avoid late binding if possible so you could try this... Public Sub Start() Dim fnt As Font Set fnt = Worksheets("Sheet1").Range("A1:B2").Font SetFormat fnt End Sub Public Sub SetFormat(fnt As Font) With fnt .Size = 14 .Bold = True...

cleaned up... Public Sub SetFormat(rng As Object) With rng.Font .Size = 14 .Bold = True .Color = vbRed End With End Sub

This works in Excel... Public Sub Start() Dim rng As Range Set rng = Worksheets("Sheet1").Range("A1:B2") SetFormat rng End Sub Public Sub SetFormat(rng As Object) With rng rng.Font.Size = 14 rng.Font.Bold = True rng.Font.Color = vbRed End...

Yes... it is that time...

Oh Joy..!!! This is indeed a more expedient solution... This works & solves my bloated mdb file problem in one fell stroke - can't thank you enough Leigh - if you're ever passing through Wiltshire I'll buy you drinks all night - cheap at twice the price... this problem has been bugging me...

Hi Bob, I did go to lengths to explain that if I import the code into a blank database with no code changes - it compiles ok... this is enough to prove that it is an Access bug. Post the code..? tricky - there are 200+ code modules - @14,000 lines of code. Also I don't think the client would...

What do you mean by 'match all the txt files ina new folder' ..?

There is a definite Access bug here - although this message may appear legitimatly there are times when the compiler looses it totally and get it's knickers in a twist... A usual symptom of this happening is the message appearing and no code being highlighted to indicate where the error is...