Please disregard last message.  I'm watching videos again, but with pain meds in me...neck surgery....I apologize... I just watched the part where you tried to use it and it didn't work sna you fixed..I'nve been a day late and dollar shrt this past week..

Hey, no problem. I get it. I sustained an injury myself about a year ago that gives me real bad migraines. No worries!

Hey Richard, messing around with DocumentF, found that if I change an Entity in the either DocumentF or Subf the file is not moved to the appropriate folder.  Getting error message '2222' file not find. if I move the entity back to previous Entity then of course if finds it. I know just a minor bug for you, but just thought you should know if you don't.  Also, no help, just a request.  i'm attempting to put household group (list of people-children,spouse,etc) in same add.ress on the addressF in the footer.  maybe a list box so you can double click on them to go to there folder. just a suggestion. Thanks again for you and your team!

We really didn't build in a way to MOVE a document from one entity to another. There's no code in there to move those files around. Do you think this would be important? Right now you could create a new document on a different entity and then select it in the old entity's folder and have it moved/copied. We could put a "move to a different entity" on the list of options for a document. Is this something you think would happen a lot?

I don't understand what you're trying to do with the multiple people in the AddressF. That form is designed for one person's address. Different people should be set up as their own entities. Maybe a tool to copy addresses would be in order. I envision usually in a situation like that ONE PERSON is on the mailing list. For example, if you're dealing with students and parents, you'd make ONE parent on the mailing list and have their address in the database. The others would be linked via Relations.

On the DocumentF, I was importing multiple files in the Document Management (DocumentF).  Afterwards, I went down the entity list to choose which file went with the entity I choose.  The file opens fine and the form shows image of doc and description fine; however, when I choose that Entity from list, you don't notice any changes, except for the "open" button when clicked now doesn't open the file which open fine before I choose the entity. As far as this happening a lot, I don't know. I know now not to add a file or multiple files without first having an EntityID, and not adding to the EntityID 0 folder.

On the AddressF, my boss was wanting to have a list of people associated with the current address. Example: John Smith, 1 Main St, Fort Myers, FL 33999 and Jane Smith, 1 Main St, Fort Myers, FL 33999, kids names, etc.  When time for Mailing in the AddressF, we would go to John Smith folder and see his wife and kids in the same household with just Names in a list box.  When a mailing went out, we could put in Addressee1 Mr. and Mrs. Smith.  I'm actually using ABCD database now at my work, but the addresses are repeating. Such as example: John has auto insurance, Jane has Life Policy, Kids have 529 plans and mailing is addressed to each person, so each entity the address is typed in 4-5 times...I already found some mistakes. I'm trying to work on a EntityXAddressT now, but surgery has slowed that way down.

Adding documents via the DocumentF and assigning to people: you're right. That will definitely have to be addressed. When you change the entity, it needs to move the folder it's in.

Your address dilemma: I think an "include in mailings" checkbox would probably work well for your situation. This way if you don't want to include the same address twice, just uncheck the box for the wife's address. To copy an address to another person, we could add a "copy from" combo box which would copy the address data from one of their Related people. This way you wouldn't have to type it in multiple times. To have an Address with multiple Entities would involve a major rewrite of the database. It's a 1-to-many relationship from Entity to Address, not the other way around. You can't assign an Address to multiple Entities. We COULD add a "same as:" combo box to the address form which would essentially "link" two addresses together. For example, you could pick "same as: Jane Smith" and it would pull in her address info. Then any changes to Jane's would automatically show up on John's record. That might work. Linking two people together. Sound like a plan? I could add this easily.

I see what you are saying. I was trying to do something like GroupSubf in GroupList, but in AddressF where the AddressID was pulling Entity into list box. You are doing something like the RelationF. Yes, that sounds like plan.