Home |
Search |
Today's Posts |
#1
Posted to microsoft.public.excel.programming
|
|||
|
|||
Late Binding Excel in Access
I have a project I'm working on and am trying to convert it to late
binding to allow compatibility with earlier versions of Excel/Access. I've got my declarations and objects set up properly, but some of my statements within my code are causing problems. ..Range("D4", .Range("D65365").End(xlUp).Address).NumberFormat = "0" is one of them. Any idea why it would bug out, causing a 'Object Defined or Application Defined' error? |
#2
Posted to microsoft.public.excel.programming
|
|||
|
|||
Late Binding Excel in Access
xlup is probably undefined - with a default value of zero which probably
isn't a legitimate argument to End. use the numeric equivalent: ? xlup -4162 this will be true for all your excel constants if your automating Excel from Access. -- Regards, Tom Ogilvy " wrote: I have a project I'm working on and am trying to convert it to late binding to allow compatibility with earlier versions of Excel/Access. I've got my declarations and objects set up properly, but some of my statements within my code are causing problems. ..Range("D4", .Range("D65365").End(xlUp).Address).NumberFormat = "0" is one of them. Any idea why it would bug out, causing a 'Object Defined or Application Defined' error? |
Reply |
Thread Tools | Search this Thread |
Display Modes | |
|
|
Similar Threads | ||||
Thread | Forum | |||
Late binding to Excel from Access causing Object error | Excel Discussion (Misc queries) | |||
Late Binding examples of binding excel application | Excel Programming | |||
late binding in excel | Excel Programming | |||
late binding in excel | Excel Programming | |||
EARLY binding or LATE binding ? | Excel Programming |