By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
435,426 Members | 3,118 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 435,426 IT Pros & Developers. It's quick & easy.

copying control field from one table to another good or bad?

P: 158
Ok I am seriously starting to scare myself with this one. I've only been dealing with Access 2007 since August of 2009 and being a newbee I made a lot of mistakes but learned a lot since then. My question today is about copying a control field from one table to another, is this a good or bad thing?

I am asking because I was adding a multi select control field from one table to another which carry the same value in both table and figured because it is the same I'll save time as it is already setup with everything and paste it into another table in the design view.

I;ve been doing this for a while now and never had any problem until today when I saw that Access was asking me for a relation which totally wasn't part of the table and form I was working on? I was adding a multiselect combo box for employeeID in a table called Project Schedule and when I dragged the field into my form it asked me what relationship this new field has with Appointment table which is totally not related or has anything to do with the project table. I've changed control names, moves one control from a form to another countless times since I started building my database and now that I have put hundreds of hours into it I am starting to feel a bit nervous about all this. can anyone reassure me please.
Feb 15 '10 #1
Share this Question
Share on Google+
2 Replies

Expert 2.5K+
P: 3,072
When things like this happen, I start with creating a new empty database and import all objects from the "strange acting" database.
This will take care of certain "loose ends" in the access internals.

I also create a new version of my important databases when I start a new editing round. The more the better, as you can lose a lot of hours when a database gets corrupted.

Feb 18 '10 #2

P: 158
I will definitly be doing that when I am done building it, thanks for the tip. As for backing up, I am the king of backup. Before any change is made to anything except format I back up on my hard drive, then a second copy on a UBS drive and a third copy at the end of each day to another computer and at the end of the week a backup is made at another location out of this building. I don't know how many times I;ve said to myself "Thank goodness for making a copy of my backups backup. For anyone out there ----- backup as much as you can handle, you wont regret it.
Feb 18 '10 #3

Post your reply

Sign in to post your reply or Sign up for a free account.