Re: Cross-Access-platform databases 're-compiles' or refreshes references for a long time

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

Hi,
best approach for you - is to develop using Access 2000, then it will work on any later version. if this is not possible - then every time you have to decompile it on Access 2000 and then compile again on 2000. Also make sure that you are using the ADO version installed on all PCs (I think Access 2000 used ADO 2.1)

--
Best regards,
___________
Alex Dybenko (MVP)
http://alexdyb.blogspot.com
http://www.PointLtd.com

"Lystig" <Lystig@xxxxxxxxxxxxxxx> wrote in message news:uAAnuiSSHHA.4188@xxxxxxxxxxxxxxxxxxxxxxx
Hi All,

I'm developing accounting software on Access. It will run on Access 2000, XP, 2003 and 2007 but only after spending a long time doing something 'fishy', if moved from one version of Access to another.

The program is developed on Access 2003. After distribution it may be loaded into Access 2002 or 2007 for execution. Here Access will hang for about 20 minutes using full processor capacity. But eventually it finishes and the application works with no problems at all. Unfortunately very few people have the patience for the initial 20 minutes and kills Access before it finishes.

First I thought it was some recompiling - but a full compile in vba takes only 5-10 seconds. Maybe it is checking up the references all over the application and recompiles.

Some statistics:
The adp-file reference 7 libraries
contains 480 forms, 215 reports and 30 code modules.
Uncompiled it uses 14 MB - compiled and compacted 23 MB

Searching MSDN for articles gives no results - it is often hard to find articles which addresses cross-product problems.

Any ideas for further diagnostics - or even an article which references this problem??

Thanks in advance.

Best regards
Stig Andersen

.

Relevant Pages

  • Cross-Access-platform databases re-compiles or refreshes references for a long time
    ... I'm developing accounting software on Access. ... First I thought it was some recompiling - but a full compile in vba takes only 5-10 seconds. ... Maybe it is checking up the references all over the application and recompiles. ... Searching MSDN for articles gives no results - it is often hard to find articles which addresses cross-product problems. ...
    (microsoft.public.access.modulesdaovba)
  • Re: Thread and subject changing
    ... attribution from a message in an old thread/subject. ... reference to the articles you're quoting. ... References header or attribution line. ...
    (news.software.readers)
  • Re: translation functions
    ... The Compile option turning gray is normal: ... Doug Steele, Microsoft Access MVP ... None of the references are missing ... then go back in and unselect the reference you just added. ...
    (microsoft.public.access.gettingstarted)
  • Re: Library Database
    ... in the same folder location as the front-end database when you ... set the reference and compile the front-end MDE, ... Two of the libraries also reference ... all of this by simply not using references, ...
    (comp.databases.ms-access)
  • Re: Names of textboxes on tab-pages within a tab control?
    ... Compact the database to get rid of this junk: ... Uncheck any references you do not need. ... Still in the code window, choose Compile from the Debug menu. ...
    (comp.databases.ms-access)