A
Atlas
I've just came out from a strange situation, would like to share with you
others.
My (.adp) project, lately had a strange beheaviour: at startup a long (5
secs delay) was happening.
I thought this was due to the (medium) complexity of the project (My app now
has 19 tables, 23 forms, 4 reports); the delay was happening even if
starting the project in a disconnected state and bypassing startup code
(holding shift).
I've tried this:
1) I 've created a new empty .adp project bound to the same sql server
database
2) I've manually imported all the forms and modules
3) I've set the proper references in the VB Editor
4) Converted the project to AC2003 format.
Now, not only the project opens immediately (the delay has gone) , but also
filesize has dropped to 1MB versus the ("compacted and repaired") old
project's 2,6MB.......
What the hell happened? Is that normal? What the extra 1,6 (even if
compacted) was for?
Is this normal? Do we have to worry about this beheaviour? (reliability?)
Bye
others.
My (.adp) project, lately had a strange beheaviour: at startup a long (5
secs delay) was happening.
I thought this was due to the (medium) complexity of the project (My app now
has 19 tables, 23 forms, 4 reports); the delay was happening even if
starting the project in a disconnected state and bypassing startup code
(holding shift).
I've tried this:
1) I 've created a new empty .adp project bound to the same sql server
database
2) I've manually imported all the forms and modules
3) I've set the proper references in the VB Editor
4) Converted the project to AC2003 format.
Now, not only the project opens immediately (the delay has gone) , but also
filesize has dropped to 1MB versus the ("compacted and repaired") old
project's 2,6MB.......
What the hell happened? Is that normal? What the extra 1,6 (even if
compacted) was for?
Is this normal? Do we have to worry about this beheaviour? (reliability?)
Bye