Brendon 05-02-2002, 07:51 PM Hi all,
I am currently developing an application which will require the use of a database. The application is already done and the exe file is only about 300KB.
The problem is that I am using MSACCESS as my data source and using ADODB to connect to it. If I were to package it with the required ADODB stuff, the installation package will hit sky-high in terms of size! My app is a very small app and therefore, such a huge installation packageg doesn't make sense.
Anyone has got any ideas?
Thanks and regards,
Brendon
Thinker 05-02-2002, 08:04 PM The size of the install has nothing to do with the size of the App.
Also, the size of the exe is meaningless, since the minimum
required vb runtimes are already 1-2mb. So, since distribution is
already pretty much beyond the size of a single floppy, you don't
really need to worry about it. If you want, don't bother including
the mdac_typ and associated files, instead, send people to the MS
web site to download and install them. Not very friendly, but it
will keep your install smaller.
Brendon 05-03-2002, 03:02 AM Hmm..... then any suggestions about what other forms of databases can I use? Any opensource ones which are small and yet can be used with VB?
Rezner 05-03-2002, 07:54 AM Originally posted by Brendon
Hmm..... then any suggestions about what other forms of databases can I use? Any opensource ones which are small and yet can be used with VB?
Well, I don't think you're going to find anything better or more efficient than Access. Another option would be to use textual files to house your information, which is obviously not a very good idea.
You could refer them to the Microsoft website like Thinker said or use CDRs as for distribution (that would be my choice.) Blank CDRs are about the same in price (if not less expensive) as a floppy disk, however you will have upwards of 700MB to play with.
Thinker 05-03-2002, 08:07 AM As Rezner said, flat random access files are the only alternative
that won't significantly add to your dependencies. However, to
code all the needed indexing to make them work like a database
(not to mention the code to access them) will make your app much
larger, and require a great deal more development time. This is
what I call reinventing the wheel.
reboot 05-03-2002, 08:38 AM The only suggestion Thinker and Rezner left out is, don't use VB. VB is a tradeoff, and has been since day 1 of its introduction. There's very little realistic way to reduce the size of a VB install. So if you can't live with that, don't use it. *shrug*
Thinker 05-03-2002, 09:07 AM That would certainly get rid of the VB run-time dependencies, but
it wouldn't help with the database dependencies. Even if one
used OLEDB with C++, I am pretty sure mdac_typ.exe still needs
to be part of the install. There are probably other options that
would be smaller if the database requirements aren't great.
There is a post here that talks about a different type of basic
(PowerBasic) that has some b-tree indexing either built-in or as
an add-on.
http://www.visualbasicforum.com/showthread.php?s=&threadid=23554
reboot 05-03-2002, 10:53 AM That would certainly get rid of the VB run-time dependencies, but it wouldn't help with the database dependencies.
Quite true. Maybe I should have said "Don't use Windows". :)
Brendon 05-05-2002, 07:36 PM Come to think of it, I think all of you are right! Just as Thinker had said, it's kinda like re-inventing the wheel, I suppose this is unavoidable. Anyway, does anyone knows if the mdac_typ.exe comes with which version of microsoft windows? What are the versions which comes with this pre-installed?
Thinker 05-06-2002, 07:31 AM You can do some research here...
www.microsoft.com/data
www.microsoft.com/data/download.htm
All the files are available for free download.
Robby 05-06-2002, 10:09 AM MDAC_TYP.exe doesn't ship with any Win OS...
You can find the details HERE (http://support.microsoft.com/servicedesks/fileversion/dllinfo.asp?sd=MSDN) , (type in "mdac_typ.exe" in File NAme:)
Brendon 05-06-2002, 07:42 PM Thanks for all the help.... :D
|