Corrupted Forms \ Reports

[joeKra]

Hello everybody ,
there is a long time having this issue, whenever i am trying whether to copy or just open my database in a shared network, some forms and reports will not open until i open it in design view and do any minor change i.e. move a textbox, i searched over the internet many hours (days) and cannot find out what causes the corruption, i am using access 2010,

thanks in advance,

 

[Rx_]

http://www.access-programmers.co.uk/forums/showthread.php?t=217619
For Access 2010, there are some other issues you can read about.
The code can use a nudge.

However, in the past I have had something like your issue. It can manafest itself in different ways. Compact and repair will not solve it.

Since you are using Access 2010, th questions of - did you just open an old version with Access 2010 or did you Import all objects? Importing all objects is the prefered way.

This is what I suggest you do.
Make a copy of your database. Use compact and repair.
Open a brand new empty fresh Access 2010 database project.
You can match the startup properties to match your orginal later.

Look up Import All Objects. So, import all your forms, tables, queries, macro and code from your existing DB project to your new project. (then go and set your start up form and so on)

My suggestion is to do this first and see if the problem still exists.
If this works, we don't need to know what actually caused the corruption in the first place. LOL

Another tip: Don't do this on a Network drive. Have both your orginal copy and the new project on your local workstation. Network latency in theory should not affect anything... in theory. Jus tremove the newtork as one of the factors during the import all objects.

 

[missinglinq]

http://www.access-programmers.co.uk/forums/showthread.php?t=217619

...Another tip: Don't do this on a Network drive.

A network drive should only be used to store the Back End, where the Tables/Data reside, of a Split Database. A copy of he Front End of a Split Database, containing everything except the Tables, should be on each user's PC.

Never, never, never should multiple users be sharing an non-split Access app on a Shared Drive! Among other things, it will lead to corruption! Sometimes it will work fine for extended periods (the record, I believe, is 14 years!) but sooner or later corruption will occur, and once it does it becomes chronic and recurring.

Linq ;0)>

 

[joeKra]

Hi i tried this all and unfortunately the problem still persist, whenever i copy the DB to my partner i have to open several Forms\Reports in design view to get them to work, any advise?

 

[Rx_]

Is there any way to import the minimal amount of tables, forms and reports into a new database; verify the same problem exist and upload it to share?
Be sure to go into the tables and remove or edit any data that should not be shared.

If you Import the minimal amount and find out that the problem does not exist anymore, then import the next one, test it, import the next one and have the problem - that would be of interest.

Just make sure NOT to send any private or company data. I just loaded Windows 7 and Access 2010 sp1 on a new portable at home. It would be interesting to try.

 

[joeKra]

Thank You i will start to work on this,

1 funny part is, that if i am opening the same dataBase from another computer via Network (don't worry i am not using the same database for all users, it's just a funny happens) it will have the very same problem i.e. on computer A it will work and Computer B it will not even it's the same instance....

 

[mlswyo]

Joe, I doubt that I can help you any but maybe you or someone that reads about your problem can help me. I've worked on an Access application now over nearly nine months and just get to the point of implementing it and boom something I did has screwed up every one of my forms. I go to my backups and they to have the same problem. I think I've traced it to MS Forms 2.0 getting getting into my references. I has altered every one of my command buttons. I finally decide that i'd better learn how to use this but can not find a single thing that is very helpful at my level. I need to talk with some one that knows a bit about this library.

Hope you get your situation resolved.

Merrill

 

[vbaInet]

You haven't mentioned two things:

1. How is the db shared? Network wise, how it's accessed and whether it's split?
2. You said some reports will not open, does that mean some open normally?
3. What view do you try opening the problem reports?

 

[missinglinq]

...whenever i copy the DB to my partner i have to open several Forms\Reports in design view to get them to work...

In addition to vbaInet's questions, exactly how are you doing this copying?

Linq ;0)>

 

[joeKra]

1. The BE is shared via network the FE is local,
2. The reports which opens will open normally,
3. I am trying to open it in report view,

I tried to copy 2 ways, copy - paste, import all objects, i also copied every form to a new form including the code's and appeared to get a new problem, that the header of the form didn't show up in form view, but the form itself worked untill i released a new update,

in one word - after any modifications from my computer (so far I didn't tried with other computers) some forms \ reports will get corrupted

notice: i just re-installed Access without any SP should i leave it so or i need to install it?

 

[vbaInet]

What if you SaveAsText and LoadFromText?

Is there anything common between these failing reports?

 

[Rx_]

http://www.access-programmers.co.uk/forums/showthread.php?p=1108074#post1108074

One of the reasons I post code (at the expense of being called 'wordy') is so I can find my own code later. Back in 2009, I had some reports with linked tables to SQL Server 2000 corrupt. When I linked them with code, the problem seemed to go away.
My personal notes indicate that it was assumed to be the new ODBC drivers.
That said, it is one more small part of that problem I had long forgotten.