Minty
AWF VIP
- Local time
- Today, 19:24
- Joined
- Jul 26, 2013
- Messages
- 10,725
Lots of good suggestions here.
I agree with @Pat Hartman - If this simply a "nice" display feature to have but no one is really benefiting from it, then remove it.
I recently had a client that wanted a list of suppliers and part numbers concatenated for use into an Excel export.
If I ran the query on one part it was fine. On an assembly with 100 + parts in it, it was slow.
And at the client end unuseable.
So I ended up doing what @MajP suggested, created a table with all the concatenated results in it.
It wouldn't run with the BE data on a network, I had to copy it on local copy tables then copy it back to the backend, and then manage any updates on the forms concerned. Real PITA, but the only viable solution.
The same process on SQL server BE was almost instantaneous by comparison, as it has a native function for it (String_Agg) .
I agree with @Pat Hartman - If this simply a "nice" display feature to have but no one is really benefiting from it, then remove it.
I recently had a client that wanted a list of suppliers and part numbers concatenated for use into an Excel export.
If I ran the query on one part it was fine. On an assembly with 100 + parts in it, it was slow.
And at the client end unuseable.
So I ended up doing what @MajP suggested, created a table with all the concatenated results in it.
It wouldn't run with the BE data on a network, I had to copy it on local copy tables then copy it back to the backend, and then manage any updates on the forms concerned. Real PITA, but the only viable solution.
The same process on SQL server BE was almost instantaneous by comparison, as it has a native function for it (String_Agg) .