![]() | |
![]() |
| | Thread Tools | Display Modes |
#11
| |||
| |||
|
|
Per Bob Barrows: Well, aside from guessing that the error is occurring in the IsBizDay function (not clear why you have a Variant argument there, rather than the expected Date ...), I really can't tell any more. Can't you step through the code to figure it out? Without knowing exactly what the input arguments were, we haven't a chance in hell of determining the cause. I should have emphasized the " Access throws this: http://tinyurl.com/486rcv8 - which to indicate a missing reference, except that the "reference" would be by the application to itself." part. |
|
I really don't think it's around typing bc the routine has worked all these years. That may sound hokey... but it seems to me like the "missing reference" error trumps all. I suspect that once I explain/fix that, the problem will go away. |
#12
| |||
| |||
|
|
Per (PeteCresswell): This routine has been working in the past - and is used daily in production.... but not today.... -) FWIW, I'm putting my money on a corrupt form. |
#13
| |||
| |||
|
|
Do you decompile regularly? If not, why not? I |
#14
| |||
| |||
|
|
Per David-W-Fenton: Do you decompile regularly? If not, why not? I It's like a religion with me: multiple times per day. I suffix my development versions with a letter and every time I take a break or something, I zip up the current version, move the .ZIP to an archive location, /Decompile, Compile, and then Compact/Repair into the next-lettered version. |
#15
| |||
| |||
|
|
On 19/01/2011 14:55:14, "(PeteCresswell)" wrote: Per David-W-Fenton: Do you decompile regularly? If not, why not? I It's like a religion with me: multiple times per day. I suffix my development versions with a letter and every time I take a break or something, I zip up the current version, move the .ZIP to an archive location, /Decompile, Compile, and then Compact/Repair into the next-lettered version. Intersting, because I have seen numerous postings on this NG that the automatic compact & repair on closing a Db is a bad idea. Are you suggesting it is a good idea if you have decompiled first? |
#16
| |||
| |||
|
|
Phil wrote: On 19/01/2011 14:55:14, "(PeteCresswell)" wrote: Per David-W-Fenton: Do you decompile regularly? If not, why not? I It's like a religion with me: multiple times per day. I suffix my development versions with a letter and every time I take a break or something, I zip up the current version, move the .ZIP to an archive location, /Decompile, Compile, and then Compact/Repair into the next-lettered version. Intersting, because I have seen numerous postings on this NG that the automatic compact & repair on closing a Db is a bad idea. Are you suggesting it is a good idea if you have decompiled first? Automatic CR on close is a bad idea, but that's not what Pete's doing. He first makes the critically important backup BEFORE doing the other things. Auto CR skips this steo so if anything goes wrong with the CR, you're dead. I would consider moving the Compile step to after the CR step, but I think his procedure is absolutely safe and sound. -- Marsh |
#17
| |||
| |||
|
|
Intersting, because I have seen numerous postings on this NG that the automatic compact & repair on closing a Db is a bad idea. Are you suggesting it is a good idea if you have decompiled first? |
#18
| |||
| |||
|
|
I close the thing, open it up again with /Decompile, compile it, close it, and then compact/repair. |
#19
| |||
| |||
|
|
I would consider moving the Compile step to after the CR step, but I think his procedure is absolutely safe and sound. |
![]() |
| Thread Tools | |
| Display Modes | |
| |