Jim,
That's what I am suggesting. IT protocols will (should take care) of routine backup of all production files. I'm curious how the problem you have described could have affected the file in your development folder which presumably should only be accessed read-only in the event of having to resort to backup.
Glenn
From: MS_Access_Professionals@yahoogroups.com [mailto:MS_Access_Professionals@yahoogroups.com] On Behalf Of Jim Wagner
Sent: Monday, January 6, 2014 11:52 AM
To: MS_Access_Professionals@yahoogroups.com
Subject: Re: [MS_AccessPros] VBA Code is missing
The backups are automatic with the network and are based on IT Protocols. I guess we could keep our own backups. We are really good about keeping separate versions. When we make changes we make a copy of the database and put that in a folder named Current. then we make another copy of the database and put that in the development folder. That way if we mess up the development version we can go back to the current version we copied.
Jim Wagner
On Monday, January 6, 2014 9:37 AM, Glenn Lloyd <argeedblu@gmail.com> wrote:
And, climbing into my pulpit, all the more reason to keep proper backups (especially of the frontend) isolated from the day to day users, and to have separate development and production versions.
Glenn
From: MS_Access_Professionals@yahoogroups.com [mailto:MS_Access_Professionals@yahoogroups.com] On Behalf Of Liz Ravenwood
Sent: Monday, January 6, 2014 11:33 AM
To: 'MS_Access_Professionals@yahoogroups.com'
Subject: RE: [MS_AccessPros] VBA Code is missing
We have 2007 and 2010 here and 2 individuals who have accidentally opened a db in 2010 and then back in 2007 have lost all of their vba code – never to be recovered.
If you open a db in 2010 and then back in 2007 you'll get unrecognized database format.
It is a tricky thing. A bit scary.
From: MS_Access_Professionals@yahoogroups.com [mailto:MS_Access_Professionals@yahoogroups.com] On Behalf Of Jim Wagner
Sent: Monday, January 06, 2014 9:10 AM
To: MS_Access_Professionals@yahoogroups.com
Subject: Re: [MS_AccessPros] VBA Code is missing
I tried to do one at a time into a blank database and it causes the errors. I think it is because the vba code is missing.
Jim Wagner
On Monday, January 6, 2014 8:50 AM, Glenn Lloyd <argeedblu@gmail.com> wrote:
Jim,
Did you create a new blank database to import into? Are any modules showing in the database window of the file you are trying to import from?
You may have to try importing the objects one by one.
Missing vba code should not cause name conflict errors.
Glenn
From: MS_Access_Professionals@yahoogroups.com [mailto:MS_Access_Professionals@yahoogroups.com] On Behalf Of Jim Wagner
Sent: Monday, January 6, 2014 10:37 AM
To: MS_Access_Professionals@yahoogroups.com
Subject: Re: [MS_AccessPros] VBA Code is missing
I think it is giving me errors because the vba code is missing. Could that be the issue?
Jim Wagner
On , Jim Wagner <luvmymelody@yahoo.com> wrote:
Glenn,
Love your analogy. Pretty harsh but true.
I have tried to import all objects into a empty database and I am getting Name conflict errors.
Name conflicts with existing module, project, or object library.
No current record.
Jim Wagner
On Monday, January 6, 2014 8:21 AM, Glenn Lloyd <argeedblu@gmail.com> wrote:
Unfortunately Jim this is one of those cases where the corrective action is not simply nice as long as everyone agrees they want it. If the databases were implemented using a true database server, it would be a non-issue because the frontend in those cases is always separate from the data storage.
The analogy may be a bit extreme but ask yourself what would happen if the building had to be evacuated during the course of a major meeting. Would you say, "Oh, Ok , you guys can stay where your are if you are not comfortable with leaving just now."
Glenn
From: MS_Access_Professionals@yahoogroups.com [mailto:MS_Access_Professionals@yahoogroups.com] On Behalf Of Jim Wagner
Sent: Monday, January 6, 2014 9:52 AM
To: MS_Access_Professionals@yahoogroups.com
Subject: Re: [MS_AccessPros] VBA Code is missing
Glenn,
This has been a touchy subject here. I do not think that they will let me do it because it is different and a change. I am at the mercy of the protocol of hesitation. I was able to do it for another department we support and they loved it. But our department is different. We have some that refused to have Office 2010 installed and got away with it for a long time until it became an issue with compatibility.
Jim Wagner
On Monday, January 6, 2014 7:43 AM, Glenn Lloyd <argeedblu@gmail.com> wrote:
Jim,
Even for single users, the application should be split. This enables you to keep an backup on a local system, isolated from the network and other users. This copy can be used as the starting point for future development as well as insurance against catastrophes such as you have just experienced.
As far as I can see, your only remedy is to track down a network backup copy that predates the first occurrence of the failure and start from there. Use that file to create a front end and then link the new frontend to the data. Once you have that working provide the new frontend to the users and link these to the backend. You should also do a compact and repair or the backend. Before you do anything, however, backup your existing files.
Glenn
From: MS_Access_Professionals@yahoogroups.com [mailto:MS_Access_Professionals@yahoogroups.com] On Behalf Of Jim Wagner
Sent: Monday, January 6, 2014 9:28 AM
To: MS_Access_Professionals@yahoogroups.com
Subject: Re: [MS_AccessPros] VBA Code is missing
Glenn and John,
We support over 50 databases located on a network.Sorry I used that sentence. The database in question is shared between 3 users and it is not split. They are not in the database at the same time. I do have a backup and when I open that, I get the same error messages.
The first message refers to a report that is loading and if I want to continue loading the project. The report is not set up to load at start up.
The next message is about the vba being deleted.
Jim Wagner
On Monday, January 6, 2014 7:03 AM, John Viescas <JohnV@msn.com> wrote:
Jim-
If the "code" part of the database is shared on your network, then that's your problem. Anyone could have done something to corrupt the database. I hope you have a backup!
You could try running decompile against a copy of the database to see if that restores the code. You could also try importing all the objects into a new, empty database.
Best of luck.
John Viescas, Author
Microsoft Access 2010 Inside Out
Microsoft Access 2007 Inside Out
Microsoft Access 2003 Inside Out
Building Microsoft Access Applications
SQL Queries for Mere Mortals
(Paris, France)
On Jan 6, 2014, at 2:30 PM, Jim Wagner <luvmymelody@yahoo.com> wrote:
Hello all,
I have been off on vacation for a couple of weeks and I came back to an email from my boss that none of the buttons in one of the databases we support do not work. So I went to the database this morning and no buttons are working. I went to alt -F11 and the vba window came up empty. I went to the onclick event of all the buttons and there is no code between the Private sub and end sub for any of the buttons.
The database is on a network and I have only seen this before when we converted from 2007 to 2010. Far removed from that scenario, I am questioning why I am now playing "Where's Waldo" with the vba code?
I will ask what anyone saw or did, but what do I tell my boss?
Thank You
Jim Wagner
This email (and all attachments) is for the sole use of the intended recipient(s) and may contain privileged and/or proprietary information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message.
| Reply via web post | Reply to sender | Reply to group | Start a New Topic | Messages in this topic (22) |
Tidak ada komentar:
Posting Komentar