Aaron Scott-Boddendijk wrote:
>
> >> How do you deal with the situation where a customer may not have
> >> the *.olb files registered. I haven't had any luck registering them
> >> manually... [This is said with a very large 'not an OLE expert' hat on]
>
> > ( I've got one of those hats too... )
> > We pretty much took the attitude that we could write software that would
> > work if Excel was installed correctly, and asserted that installing
> > Excel correctly meant OLE would work (I can't think of any detail of
> > what constitutes a standard Excel install now though. Question for your
> > System Admin?). Otherwise there is a Massive amount of ground to cover,
> > eg. if they aren't registered, what if they aren't in the correct dir?
> > Not on the machine? Old versions? Later versions? Dependencies? ...
>
> The *.olb files are COM type-libraries... You can have a perfectly working
> OLE layer without the olb files installed (I believe they're only installed and
> registered if you select 'Visual Basic for Applications' support...
(Lucky I put my hat on quickly ;)
What I should have said was that we made an app. that could use OLE
under
certain (specified) conditions. Meeting those conditions was considered
a setup issue which we would deal with separately. We effectively
lumped
the reg./non-reg of the *.olb files with any other OLE Or Excel issues
that
could have come up, expecting there was Bound to be something that would
break somewhere. We also had the luxury that the machine where it was
to be
installed was also being used for user-acceptance testing (this is
getting more
and more to be a special case). So from above: They Had to have the
*.olb files
or our app. wouldn't work. (Can't remember any specifics, but there
were
several other files that had to be there as well (possibly even specific
versions?).) If they weren't there, at that stage we would look into
the
best way of getting them there.
>
> I've tried copying the *.olb files to the Excel folder and executing regtlib on
> them and although it said registered it didn't work with Delphi...
Beyond me here.
>
> It's a shame because the compile-time checking and they ability to directly
> create elements like font objects is really handy...
Beats fighting with variants...
>
> --
> Aaron Scott-Boddendijk
> Jump Productions
> (07) 838-3371 Voice
> (07) 838-3372 Fax
>
> ---------------------------------------------------------------------------
> New Zealand Delphi Users group - Delphi List - [EMAIL PROTECTED]
> Website: http://www.delphi.org.nz
--
---------------------------------------------------------------------------
New Zealand Delphi Users group - Delphi List - [EMAIL PROTECTED]
Website: http://www.delphi.org.nz
