Likely be able to assist you, but I doubt anyone has one to just hand over?I have several databases that has similar structure and I need module to browse and update existing records if changed or insert new records to the current database from others!!!
can anyone help?
Can you explain in a bit more detail the purpose of the database and the 5 copies?yes
the structure is similar
files are copy
my issue is key fields !
one of tables does not have key field
have three field that triple field together makes record uniq
(textcode, bookcode, bookpage)
This is especially important if you have any null values in import or destination tables.This article may also be useful for synchronising data where the fields do not involve a primary key
Null is the absence of a value. a field can appear to be "empty" in one of two similar, but different situations.This is especially important if you have any null values in import or destination tables.
This is because a null value is not equal to anything else NOT even another null value.
some field in my tables are empty!!! Is this null?
Probably ...but they could also be zero length strings. Either way, the approaches in the article may help.This is especially important if you have any null values in import or destination tables.
This is because a null value is not equal to anything else NOT even another null value.
some field in my tables are empty!!! Is this null?
loaded!!We have a source book where we find phrases in other books and refer to it
Each of the researchers may have added a reference phrase on it.
Our tables have keys, but it is possible that there is no match in the keys and they are not uniqueView attachment 111363
how can i use compond join in query?Your description is a bit thin. Do you have control over all of the databases? I.e. can you make design changes such as adding an index if you don't have one?
A 3-component compound key is perfectly possible in Access. You just need to specify the correct values for the WHERE clause. Usually (for simplicity of design) you would prefer a way to JOIN a table using one field from each table for the linkage. With three participants in the key field combination, that becomes trickier, though not impossible. However, as long as the record can be uniquely specified, you should be OK.
Since we don't know much about your data, we have to offer more general advice. It would improve performance tremendously if that three-part combination has individually indexed fields, but using a WHERE clause, you can even manage non-indexed compound key fields. You just might wish they were indexed later since part of your problem will be identifying whether a matching record exists (prior to inserting a copy). For that, indexes will be your friend and will keep you from going slowly insane, as there is nothing slower than a sweep through non-indexed records as you do what we call a "relation scan" - translation: picking your way through unindexed records to find something.