Jump to content

Recommended Posts

Posted

Hi,

Looking to see if someone can help,

We have junior librarian 3 v 3.2.2.29 and now when we try to do stuff we get a error message saying.

 

Modul : Class:System.Recordset_library

Error : Reccord is deleated

Number: 3167

Source: DAO.database

 

Phoned the help desk up but no luck as we no longer have a support contract with them... So i have left it between the school and MLS to sort that out.

 

But just wondered if anyone had any ideas on this?

 

Cheers

Posted
When was the last backup? If it was recent, you might be better off reinstalling and restoring (assuming you have the installers). Most of my schools have pretty vanilla installs, so this might not be an option if you have a "fully loaded" system. Maybe try a fresh install on another machine just to see what you get restored?
Posted

On your install CD in the Extras folder there is a repair tool, run that and it should fix it.

If not you will need to refer to a backup or MLS Support.

  • 2 weeks later...
Posted

Ok all them options dont work.

 

If i was to install junior librarian again on a laptop and the TA inputs all the books again. Can I then make a back up of that Database/datafile and reinstall junior librarian on the library pc and import that database?

Posted
The problem isn't with your installation. The access database junior uses has become corrupt, if the repair tool didn't work I suggest you contact MLS as they have tools that may be able to recover it.
Posted

Cheers Bennz,

 

We have contacted them, but they wont even let us speak technical to them as the school haasnt paid the support contract.

To get this reinstaited they are quoting over £1000 which we the school are not prepared to pay.

Posted

Guess the school better start looking for a new product then.

 

Unless you can prove it's faulty software then I'm not surprised they won't help without a support contract.

 

Ben

Posted

Adding a note here for future reference and search results ..

 

this issue was caused by a record being deleted from a table in the database, causing orphaned records in other tables - even tho referential integrity was on!

 

resolution was:

1. break the table relationships

2. rename the tables containing the orphans to OLD

3. Create new tables

4. Rebuild the relationships

5. Transfer data from OLD tables back into the new tables

- orphaned records will not be permitted back into the new tables because of the ref integrity rules that apply (which should have prevented the original deletion anyway!!)

  • Thanks 2
Posted

If you find the database password (not that I condone that sort of thing) then the database structure is fairly easy to fix.

 

Not that I have ever done it of course but I have a friend that I think knows someone who.... :)

Posted

Just to update,

thanks to detjo this is now up and working again, now just looking at away of making the backups a bit more failsafe and taking them away from the librarian to do.

 

CESIL getting the password isnt that difficult there are programs out there that can help but im thinking it may be the same for all of them. It would be the recreating the database which would be my problem as we dont have access to access anymore.

Posted
Just to update,

thanks to detjo this is now up and working again, now just looking at away of making the backups a bit more failsafe and taking them away from the librarian to do.

 

There's an automatic network backup buried in there somewhere...

Posted
There's an automatic network backup buried in there somewhere...

Yes there is...I have it set to backup to the main server so it gets included in the nightly backup.

@MattDLEA I can see that if you don't have access to access then fixing an access database would be trickier :)

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...