Thank you David for the suggestion. Actually that was one of the things I was worried about. So I did build a small test application with the same database. It did everything my main application did except it did not do anything fancy like accessing the Jpeg data. This one installed and worked ok on the other PC which is also a Windows XP with MSOffice 2003 installed. It is a interesting question. If Jet is not supported in the current products, then I have to work around it I guess.
Anu Rang, TotallyFreeEnergy http://totallyfreeenergy.freehoxt.com --- In [email protected], "David H Bolton" <[EMAIL PROTECTED]> wrote: > > > ----- Original Message ----- > > So atlast I figured out (I mean the folk here in the forums figured > > it out) that I needed to get a dynamic connection string and relative > > paths. It worked ok. It built and executed without any complaints on > > my pc. I got the installation module built with no errors. It > > appeared to install ok on another equivalent PC. But when I tried to > > fire up my application I get a Microsoft crash message. I just cannot > > figure it out what else can be going wrong here. I got a > > ADOConnection object with the connection string being built on the > > fly. A ADOTable object that connects to the connection object on the > > fly. A Datasource object which either references my ADOTable or is > > referenced by my ADOQuery objects. A bunch of Data aware components > > which connect using the ADOConnection object and the Datasource > > object. I do all the referencing and plugging in of these components > > dynamically. Builds and executes ok but when i install on another pc > > it crashes ! > > Main complication having to access some TBlobField in the database. I > > had a brain wave and did typecasting of a TField to TBlobfield. It > > worked within the IDE. I wonder if that is infact causing the mishap > > in the install build? Although why should it I cannot fathom. > > > > Anu Rang, TotallyFreeEnergy > > http://totallyfreeenergy.freehoxt.com > > > Have you checked that the MDAC on that PC supports JET? Not being funny > about Access but MS are wanting people to migrate of it. I thought the > latest MDAC lacked the JET drivers because of this. I think that's why SQL > Server Express 2005 is given away free and you can use it for commercial > applications. > > David Bolton >
