MS Access - Form Problem

ADL

ADL

ADL

Associate
Joined
27 Jun 2008
Posts
94
Hi everyone,

Sorry if this is in the wrong place and sorry if I'm asking a ridiculous question but I've scoured everywhere and whilst I can find some hints to the problem I have, there's not much in the way of solutions.

A few months ago, I was tasked with creating a database on the cheap for work with a view to storing inspections, vehicles and that kind of thing. Unfortunately, we've grown quite dependant on it (someone I warned everyone not to do) and it gets hammered and added to every day so there are now all sorts of queries, reports and thousands of records.

Now that you've got the background, I'll explain the problem! I added a button to a form I'm using as a switchboard, closed it, was prompted to save the changes, clicked yes and it doesn't close. In fact, the only way I can close it is to not save any changes I make. If I try to copy the form I get presented with a message claiming that it conflicts with another object (even if I call it something else). My panicked research last night and this morning has revealed it might be something to do with permissions but nothing has changed in the last few days for that to happen. The file is stored on a server and 4 machines in the office routinely use it along with two people who VPN into us. The only suspicious thing that occured was yesterday morning I got in and the lock file was there even though I couldn't see anyone who might have had it open.

Please help. It doesn't look like I can copy objects out (reliably) and I'm now left with a database that has a form I am completely unable to change. Not to go for the sob story but I also have a boss who demands everything YESTERDAY and goes crazy when the slightest thing goes wrong!

No pressure!

Many thanks,

Adam
 
Hi Adam,

I have over 10 years experience writing Access database's but I would need a copy of it to try and help you. Is there any way you can e-mail a copy of the database to me so that I can have a look at it? if you copy the database and then delete the data from it if it is confidential.
 
Adam,

I've just had an idea. Try creating a new (empty) database and then import all of the tables, forms, queries etc. from the original database.
 
This used to happen a lot when where i worked last year. There was always a popular database located on a shared drive locking everyione out, the lock fuile remained even after users had left.

Alwasy had to get an administrator to remove the file. Although he swore it was deleting automatically because users were exiting the database in a weird way.
 
The lock file gets left behind if the PC is switched off/rebooted without closing the database down. It usually disappears when the database is next started and closed.

It is best to copy the database before making any changes, the tables can then be imported into the modified database. My suggestion above can work if the lock file has become corrupted.
 
Hi everyone!

Firstly, can I just say THANK YOU very much to you all for helping because, I think it's sorted.

I came in this morning, read all your replies and thought - right - I'll zip it all up and send it off to Deleted member 2277 (thanks for that by the way!). But as I was doing it, I thought about copying all the forms, tables and reports into a blank database as you suggested. This seemed to work until I got to the forms whereupon I was told that I couldn't paste the form I use as a switchboard because another object exists. :confused:

All the other forms pasted in fine so clearly it was the Switchboard form causing me a problem. So I went into the original database, opened it in design view and copied everything from it into a blank form, then saved the blank form as the new Switchboard and it seems to be working.

Should have tried that before bothering all you! Thanks again for your help - you have no idea how much you've saved my skin! Keep your eyes peeled though - I've just been told we're moving all our data over to this database and using it as a permanent system. The fool! Doesn't he realise I don't know what I'm doing?! ;)

Anyway, thanks again for all your help guys - it is very very much appreciated.

Thanks,

Adam
 
I would seriously consider keeping a development database. This is the database you make changes to and test on. Once you're happy the changes work (get someone else to try them out too) then copy the forms/querie/reports over, keep track of any table changes made and mirror these in your 'live' database.
 
You must log in or register to reply here.
Back
Top Bottom