tvanstiphout
Active member
- Local time
- Today, 16:16
- Joined
- Jan 22, 2016
- Messages
- 634
Pretty easy to find information online about this error. It has nothing to do with Access, the topic of this forum.
Weird Issue (3 Viewers)
- Thread starter SykesIT
- Start date
Thanks for that obvious response. The original post was nothing to do with the last message and was issues with access database having issues.
As others have mentioned in this thread, you need to split the db and have each user be given their own copy of the front-end. Many of these types of errors (including DB in inconsistent state and VBA errors/VBA Project cannot be read, etc) will often go away or at least become much less prevalent. This advice comes from extensive experience I and many others on this forum have experienced. Additionally, even if you split the db, do not try to still share the front-end on a network share as db corruption and VBA project issues will still happen (even though the front-end may have no actual tables/data in it).
GPGeorge
George Hepworth
- Local time
- Today, 15:16
- Joined
- Nov 25, 2004
- Messages
- 3,364
I doubt that the two issues are entirely separate, but we don't have eyes on the network environment which makes diagnosing the problems more difficult.
In Post #1, you wrote, "Even if I copy the DB local I still get errors." Here, by "local" I at least thought you meant the laptop where the problem is. Correct?
In Post #18, you wrote, "On the laptop I cant even copy the file over get error invalid signature." That is the exact opposite of Post 1.
In the interest of making sure we are all on the same page, therefore, I want to be nitpicky about what is really going on.
Can you copy the Front End, i.e. the accdb containing forms, reports and VBA, of the split database application from the original computer to the laptop?
In post 1, it sounds like you originally could, and did, successfully copy the original unsplit accdb to the laptop (I assume that is what you meant by "copy the DB local".)
In Post 18, it sounds like you suddenly can't copy the accdb which contains only the forms, reports and VBA.
If that's the case, there are possible reasons for it, but rather than go off on a hunch, let's make sure we agree on the circumstances. For example, if someone else, i.e. another user, or even you, the developer, already have the Front End accdb open, Windows wouldn't let you copy it. But rather than go off on a tangent, please make sure we have the full circumstances nailed down.
In Post #1, you wrote, "Even if I copy the DB local I still get errors." Here, by "local" I at least thought you meant the laptop where the problem is. Correct?
In Post #18, you wrote, "On the laptop I cant even copy the file over get error invalid signature." That is the exact opposite of Post 1.
In the interest of making sure we are all on the same page, therefore, I want to be nitpicky about what is really going on.
Can you copy the Front End, i.e. the accdb containing forms, reports and VBA, of the split database application from the original computer to the laptop?
In post 1, it sounds like you originally could, and did, successfully copy the original unsplit accdb to the laptop (I assume that is what you meant by "copy the DB local".)
In Post 18, it sounds like you suddenly can't copy the accdb which contains only the forms, reports and VBA.
If that's the case, there are possible reasons for it, but rather than go off on a hunch, let's make sure we agree on the circumstances. For example, if someone else, i.e. another user, or even you, the developer, already have the Front End accdb open, Windows wouldn't let you copy it. But rather than go off on a tangent, please make sure we have the full circumstances nailed down.
- Local time
- Today, 17:16
- Joined
- Feb 28, 2001
- Messages
- 30,697
OK, let's ask a simple question regarding "Invalid signature." Have you tried to digitally sign the stand-alone database?
If you sign a monolithic (stand-alone or non-split) DB, the INSTANT you change ANYTHING, even deleting one extra space in one record in a table using a TRIM$() function, you invalidate the signature. A properly split front-end, on the other hand, at least potentially CAN be digitally signed. Note that a signed front-end cannot attempt to modify an object property for any intrinsic Access objects residing in that FE. A back-end can never be successfully digitally signed and then updated even in the most diminutive amount.
As noted by others, we are having a nomenclature issue, or so it seems. Several of our members read your explanations differently. We are happy to help you but if we cannot agree on the exact problem, that help is harder to offer.
If you sign a monolithic (stand-alone or non-split) DB, the INSTANT you change ANYTHING, even deleting one extra space in one record in a table using a TRIM$() function, you invalidate the signature. A properly split front-end, on the other hand, at least potentially CAN be digitally signed. Note that a signed front-end cannot attempt to modify an object property for any intrinsic Access objects residing in that FE. A back-end can never be successfully digitally signed and then updated even in the most diminutive amount.
As noted by others, we are having a nomenclature issue, or so it seems. Several of our members read your explanations differently. We are happy to help you but if we cannot agree on the exact problem, that help is harder to offer.
