Home |
Search |
Today's Posts |
|
#1
![]()
Posted to microsoft.public.excel.programming
|
|||
|
|||
![]()
Bingo. That's exactly what's happening.
I'll take a look at it on Monday when I go back in. Thanks, Tom. I knew you'd have an answer if nobody else did. :) -Donna -----Original Message----- Are you using any constants in your createdatabase expression. (such as Set nWindEx = Workspaces(0).CreateDatabase (Application.Path _ & "\NWINDEX.MDB", dbLangGeneral) ' dbLangGeneral would be "" rather than its early bound defined value of ";LANGID=0x0409;CP=1252;COUNTRY=0" (at least that is its value on my machine). or perhaps you use the createworkspace method that also uses a constant when you late bind, these constants are empty variables - they are not defined constants anymore. The will be interpreted as having value of zero (for longs, or null string for strings). this is a common problem people overlook when using latebinding - this would be particularly true in your case where you used early binding to do the development and are switching to late binding. You need to hard code values where you have constants. (or define the constants in your own code). Just a thought. -- Regards, Tom Ogilvy |
Reply |
Thread Tools | Search this Thread |
Display Modes | |
|
|
![]() |
||||
Thread | Forum | |||
Late Binding issue with Excel.Application object | Excel Discussion (Misc queries) | |||
VB Extensibility library and "late binding" | Excel Discussion (Misc queries) | |||
Creating a MailItem in Outlook from Excel using Late Binding | Excel Programming | |||
Early vs Late Binding - Word | Excel Programming | |||
DAO objects with late binding in Excel? | Excel Programming |