Recent content by suchiate

Hi dfenton, Thanks for your concern, please do go through all the posts as that issue has already been put to an end. :)

oh.. alright then, let's depend on fate to see if my topic title would interest u again in future :)

Alright, thanks for all your suggestions and advice, would you mind if I PM you in future for more discussions?

Wow! I'm impressed and motivated by your years of experience, I still have lots to learn in this field, thank you for sharing your knowledge, I'd love to learn as much as I can when I can :) Are we beginning to go out of topic? :D

Thank you very much, Doc_man, do you only use Access or you are also using SQL Server 2005 and other databases? I am thinking of migrating the system to SQL Server in future, so thinking to ask whether people still stick to Access alot or they are all slowly moving towards SQL Server and so on?

Thanks for sharing =) Currently, the old design is still running, but we are doing a parallel migration, i slowly redesign certain portions of design and codes and then they test, once tested, then migrate the certain portion to the new design and upload the new modules. Not sure if it's a good...

Alright, thanks doc and banana, I will try to understand the entire scenario of the system first as I am taking over the previous database and programmer's tasks, 1 taking over 2 :D but their design really sucked.. so I have to redesign but the system scope is so big that I think I should...

Of course, no hard feelings between us :) After all, you are just trying to give the best advice and suggestion you could to anyone =) and I appreciate that and I hope everyone does too. Actually the actual case I am dealing with is a Multi Level Marketing System, whereby members can be in...

First of all, The_Doc_Man, I am not trying to challenge and I'm especially not trying to find an argument with anyone, maybe I AM bad in expressing myself or you read with anger or can't accept certain things, but whichever, I am sorry for the misunderstanding. Regarding the AutoNumber to...

What I am raising about is not on the Physical Point of View.. but from the conceptual point of view. It is not a One-to-One relationship as the Child table, would only inherit the PK attribute from the Parent table whereby the parent table has nothing from the child table, no key or anything...

Ok I have my solution right here, I set Table1's PK as AutoNumber ReplicationID (GUID) as the FK and PK for Table2 which is Number of FieldSize ReplicationID it's a simple thing which I dont know why i never thought of.. guess i need to brush up on Access, been using too much of MS SQL.. :p...

Nah, Access wont allow relationships with different data types, AutoNumber must be related to AutoNumber. Well the reason I am doing this is because, I dont need a separate PK for a child table since it should depend on the PK of the parent table. And the reason i am doing this is because some...

So it will never work this way as illustrated? TBL1 TBL2 FLD1 (PK) ----- FLD1 (FK, PK) FLD2 FLD2A FLD3

Thanks for your reply Bob, but what I want to implement is an inheritance concept, therefore, I want the primary key of tbl 2 be the foreign key itself from tbl 1. Can that be done in Microsoft Access?

Hi Everyone, I am currently working on two tables: tbl1 ID (Replication ID), Field1, Field2, Field3 tbl2 ID (Replication ID), Field1 I have a one-to-one relationship for these two tables where tbl1 is the Primary key table. But, I cant insert any records into tbl2 as in Access it is...