Multiple Subdatasheets
- Thread starter Hey Lucy
- Start date
- Local time
- Today, 15:54
- Joined
- Sep 12, 2006
- Messages
- 15,987
Lucy
in a properly designed app, you can link any table to any other table, and show forms/subforms etc, to achieve whatever you need in an application
you had a similar thread (ie about tables) about values propagating between records in a table
the point is that very few of us ever look at tables directly, and generally never bother with the subdatasheet facility.
a couple of reasons are that tables cannot easily be sorted or filtered across multiple columns. where there are various ids pointing to related records then all you are likely to see in a table is a relatively meaningless numerical value. Additionally, data can easily be changed incorrectly by using tables directly. much better avoided.
in a properly designed app, you can link any table to any other table, and show forms/subforms etc, to achieve whatever you need in an application
you had a similar thread (ie about tables) about values propagating between records in a table
the point is that very few of us ever look at tables directly, and generally never bother with the subdatasheet facility.
a couple of reasons are that tables cannot easily be sorted or filtered across multiple columns. where there are various ids pointing to related records then all you are likely to see in a table is a relatively meaningless numerical value. Additionally, data can easily be changed incorrectly by using tables directly. much better avoided.
Hey Dave! Thanks for responding once again. You've become my go-to-guy! I like the clarification about Gemm, btw! lol
This database is obviously teaching me new things that I haven't had to use before. A challenge, but a masterpiece in the end!
I have (sort of) come up with a solution, but I need a better one, really.
Working on real estate db. Frm-All Properties has a subform Client Offers to keep up with each offer made on a property, and each offer can have multiple notes made about it, therefore I made the subform of the offers in datasheet view and then have the info from Notes table as a subdatasheet on that form. That's all fine and good and gives me what I want.
But...I do have another field on that subform for client offers that can have multiple values, and the way I had thought to do it was the same way I did with the Notes info as a subdatasheet, but since this is on the same subform I couldn't figure out how to make that work.
Instead, I created the other field (agents) as allowing multiple values, and that works, except that can create an awful long field if you have enough agents selected.
I posted somewhere else in this forum (prob general) to ask if there was any way to force a return between each value in the agents field, so that it "stacks" instead of lengthens the field. Do you know if this is possible? That would be the perfect solution to my problem, but I don't know if it's possible or how to make it work. I played around with a few things but haven't had any success with this issue.
BTW, Gemma is a beautiful dog. I used to have Huskies and Alaskan malamutes myself.
Thanks!
This database is obviously teaching me new things that I haven't had to use before. A challenge, but a masterpiece in the end!
I have (sort of) come up with a solution, but I need a better one, really.
Working on real estate db. Frm-All Properties has a subform Client Offers to keep up with each offer made on a property, and each offer can have multiple notes made about it, therefore I made the subform of the offers in datasheet view and then have the info from Notes table as a subdatasheet on that form. That's all fine and good and gives me what I want.
But...I do have another field on that subform for client offers that can have multiple values, and the way I had thought to do it was the same way I did with the Notes info as a subdatasheet, but since this is on the same subform I couldn't figure out how to make that work.
Instead, I created the other field (agents) as allowing multiple values, and that works, except that can create an awful long field if you have enough agents selected.
I posted somewhere else in this forum (prob general) to ask if there was any way to force a return between each value in the agents field, so that it "stacks" instead of lengthens the field. Do you know if this is possible? That would be the perfect solution to my problem, but I don't know if it's possible or how to make it work. I played around with a few things but haven't had any success with this issue.
BTW, Gemma is a beautiful dog. I used to have Huskies and Alaskan malamutes myself.
Thanks!
Well ttabulated forms are the standard presentation for dealing with one-to-many relationships. Yes you can use other methods but we are dealing with relational databases and that's how they work.
I may have over-baked the screen presentation but I deal with images so it is only a logical progression from a white background.
Simon
I may have over-baked the screen presentation but I deal with images so it is only a logical progression from a white background.
Simon
- Local time
- Today, 15:54
- Joined
- Sep 12, 2006
- Messages
- 15,987
lucy - i may have misunderstood. i thought you were trying to do this at table level, which I believe is best avoided
if it is a form/sub form thing, then it's all part of your interface design, and is more a matter of finding a presentation that works.
if it is a form/sub form thing, then it's all part of your interface design, and is more a matter of finding a presentation that works.
Thanks Simon and Dave. I think I am going to use the tabs for this one even though the client didn't like the way that looked. It looks a lot better than a long string of names in one field, so I'm just going to tell him it's the only way it can be done. He won't know any better and it is the best solution! Thanks for your help guys! This one has been a huge undertaking (4 months of work) but I deliver on Monday and I'm almost there! Yaaaaaaaaay!
- Local time
- Today, 10:54
- Joined
- Jan 23, 2006
- Messages
- 15,528
Do a control printScreen, open Paint or other utility (IrfanView) and paste, save as YourFileName.jpg
Go to the Reply part of the forum, below the window is a button "Go Advanced"
click it.
Go to "manage attachments"
Browse to get the correct jpg, select it, Upload
Ta da!!!
Go to the Reply part of the forum, below the window is a button "Go Advanced"
click it.
Go to "manage attachments"
Browse to get the correct jpg, select it, Upload
Ta da!!!
Attachments
Lucy,
Be bold.
I have had experience with Multi-value fields in 1989. They were fantastic for the project we were working on. Things have moved on and with the deployment of fully relational databases multi-value fields are more simply handled with another table. I started developing Access with no tabulation facility and now going without this feature would be like going without Maple Syrup.
Simon
Be bold.
I have had experience with Multi-value fields in 1989. They were fantastic for the project we were working on. Things have moved on and with the deployment of fully relational databases multi-value fields are more simply handled with another table. I started developing Access with no tabulation facility and now going without this feature would be like going without Maple Syrup.
Simon
Why thank you, JDraw. Knew how to create and save the image, just didn't know how to get it in here! Learn something new everyday.
As you can, this setup is NOT optimal, so I think I'm going to have to go to tabs. Don't have experience with tabs, so I will have to figure out how to link the Outside Agents to the correct Offer IDs. Can be multiple Outside Agents for one Offer.
As you can, this setup is NOT optimal, so I think I'm going to have to go to tabs. Don't have experience with tabs, so I will have to figure out how to link the Outside Agents to the correct Offer IDs. Can be multiple Outside Agents for one Offer.
