Arthur Fuller
artful at rogers.com
Mon Feb 10 10:05:00 CST 2003
Upon reading your message, and having written a fairly sizable app, I
decided to look at the current file size and then count the forms and
reports (since mine is ADP, your mileage may vary, since queries are stored
in the BE not the FE).
File size of ADP after compaction: 16MB
Number of forms: 315
Number of reports: 175
Number of modules: 34
IMO, the app is well-written. Of course any seasoned developer might find
flaws, and I could myself, given payable hours to do so, but even then, I
don't think I'd all that many opportunities to shave code, because I have a
lot of library code that is called from numerous places, plus I insisted to
the client that 10% of the time be devoted to code refactoring, so I got 4
hours per week to inspect my own code and decide what could be done better.
That said, last week I was refactoring and discovered three places where I
had overlooked setting an object variable back to Nothing once I was done
with it.
A.
-----Original Message-----
From: accessd-admin at databaseadvisors.com
[mailto:accessd-admin at databaseadvisors.com] On Behalf Of John Skolits
Sent: February 10, 2003 8:05 AM
To: accessd at databaseadvisors.com
Subject: RE: [AccessD] Large MDE file
Maybe a dumb question but where is the MDB version of your application? I
would say 20 Meg is a sizable application. Assuming it has no data and only
code, something like that would take a long time to develop if written well.
In addition, I wonder how well written it is. I've written some pretty large
application, but a 20 meg one is pretty big. The only possible place where I
see it getting that big with no data is if you have a lot of reports or many
forms with bitmap images.
"The MDE is becoming to large and ""slow"" to handle everything"
I believe, there are too many factors in an application to make that general
comment. With 20 megs, a lot could be poorly written.
"Also more often errors keep coming up "
In a perfect world, there should be no errors, but there is an implication
in your statement that makes me think, you've been having many problems to
begin with. All this points to a poorly written application, (Sorry if I've
insulted you, assuming you wrote the code)
I think the issues will only be worse if you convert it to VB. It's a 20 Meg
Access database application and I can't imagine the amount of work it will
be to convert. Then again it may have all unbound forms. That would make it
easier to convert but also a sure sign that the person who wrote it should
have written it in VB in the first place and never tried to do it in Access.
(Please-no attacks on that last comment, I'm a bounder!)
You need to get the MDB version and see how it was written before
considering a conversion.
That's my opinion. /Enjoy the thread/
John Skolits (ducking for cover)
-----Original Message-----
From: accessd-admin at databaseadvisors.com
[mailto:accessd-admin at databaseadvisors.com]On Behalf Of
marcel.vreuls at achmea.nl
Sent: Monday, February 10, 2003 5:03 AM
To: accessd at databaseadvisors.com
Subject: [AccessD] Large MDE file
Hi Group,
I am strugling with the following. My application is a application for
administring orders en commission revenues for agents in the furniture and
paper branche. The MDE is now about 20 MB large. This is only code. The
tables are in a seperate MDB file. This is after the following steps
1. Import the database into a new one.
2. Set the references
3. Repair-Compact the database
4. Saving it into MDE state.
The MDE is becoming to large and slow to handle everything. Also more often
errors keep coming up which are over after restarting and compacting the
MDE database. I am looking to convert the MDE to Visual Basic and have
tested some tools as VB Express en Com Express.
Is there anyone who has tips/experience in with this.
1. porting Access 2000 apps to VB and what the extra work will be (DAO to
ADO)?
2. the use of VB Express or Com Express or different programs?
3. Are there companies who have experience or could do the major part of
the conversion for me?
4. After analysing and overthinking the proces. The idea of starting all
new again is still sounding better. But the hours....pfff...
Your opinion?
Thanks, marcel
********************* DISCLAIMER *********************
De informatie in dit e-mail bericht is uitsluitend
bestemd voor de geadresseerde. Verstrekking aan
en gebruik door anderen is niet toegestaan.
Door de electronische verzending van het bericht
kunnen er geen rechten worden ontleend aan de
informatie.
************************************************************
_______________________________________________
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com
_______________________________________________
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com