Search results

Oh Oh Oh Now you have me worried! Just to note that some of those fields will not be unique to a given secondary table. They will appear in multiple tables, but the records that table relates to will not be in another table and therefore each instance in this column is only stored in one place...

Hello all, Hope somebody can help with this. I am currently trying to tidy up a large messy database. I am standardising the naming convention for tables and queries etc, as they are a mess. I want to create a form with some code perhaps, that will allow me to change the name of a query etc...

Sorry I cant help, but I have a related question. Can you create a macro that auto saves the database as a backup every hour or something like that?

Ok, Yes the users will be entering data through queries, and security isn't really a concern. The problem is that there will be more than 255 fields required and therefore the only option is to break out into tables? And the best way to link these tables is to use relationships? By the way...

Ok Thanks for that, The reason these tables have been split is because the data to be contained in the secondary tables is to be entered by people in a different departments. Typically, a few tables per department, with each table representing a recordset of tagnums that all have the same...

Hi All, I'm Looking for a bit of advise. I'm about to try and build a new database that will have about 40 tables. One of these will be the main table. This table will have a primary key TAGNUM and several other fields containing data associated with each tagnum. Most of the other tables will...