Access 2007 - VBA code disappearing

[ssissons]

I'm not sure what group this belongs in, so I am putting it in the Programming group.

We have an Access 2007 database. Users are in it at various points during the day - I don't think they are in it for 8 hours, everyday, but just when it is needed. When it is first opened, a screen is displayed which, during it's Form_Load sub, it displays another screen to select a printer. Two mornings in a row now, when they have opened the DB, it has not displayed the second screen. When I go to look at the first form's code, there ISN'T any! It has disappeared. In fact, ALL of the VBA code behind all of the forms has disappeared. No error messages are displayed.

What would cause this? Has anybody else experienced this? I have a backup copy of the DB, so I can delete the bad one, and restore it from my copy. So, I can recover. But, why?

Scott



p.s. We have other DBs that are not having this issue.

[ranman256]

Is this a .mdb ?
If its compiled (to a .mde or other) you wont see code.

But I have had this happen where the code vanished from .mdb. I never explained that.
did someone transfer the objects and forgot the code?

[pbaldy]

Is the database split? It should be; multiple users in a single copy of a db can corrupt it, which can cause your problem.

[ssissons]

Ranman -

It is an .accdb. No, I am the only one making any changes to the DB.

Paul -

It is not split. I assume you are referring to front- and back-end?

[ranman256]

Hmmm. I'm stumped. Corruption? Got a backup? (always make copies)

[pbaldy]

Paul -

It is not split. I assume you are referring to front- and back-end?

Yes, that's what I'm referring to. That would be the number one suspect in my mind. I just split a db for a client that asked me to add some functionality to an old db of theirs and they said it used to corrupt once or twice a week and it hasn't since we split it.

[ssissons]

I'll give the split option a try. Thanks!

[pbaldy]

No problem. Post back if you get stuck or let us know if that fixes it. Make sure each user has their own copy of the front end.

[Missinglinq]

You may have two separate things going on, here. As to the 'disappearing code,' in the IDE (code window) the Procedure View button may have been accidentally activated. At or near the bottom of the code window, just to the left of the Horizontal Scroll Bars, are two tiny icons, Procedure View and Full Module View. Click on the Full Module View icon and see if your code reappears.

As for splitting the app, having multiple users sharing a single, non-split database, sitting on a network drive, is the sure way to repeated episodes of corruption, as Paul said, as well as speed and timing problems, and all manner of strange, odd and curious behavior, including the problem you're having, now! Multiple users simply have to work off of a split database, with each user having their own copy of the Front End, which contains everything except the data/tables, on their respective hard drives, and a Back End with only the Tables on a shared drive.

Being in forced retirement, I spend 8-10 hours a day here and on other Access forums/newsgroups, and over the past eight years have seen literally dozens and dozens of reports of non-split databases causing these kinds of problems as well as massive data lose! The really insidious thing is that a non-split app can work for extended periods of time before the troubles begin! But once it does, they become chronic, which is to say they occur over and over and over again!

Linq ;0)>