Forum Discussion
Problem with getting CONCATENATE text combined with an IF/THEN and nested VLOOKUP to display...
So as I mentioned above the line:
IF(AND(U12>0,T12>0),CONCATENATE(VLOOKUP($U$12,W290:X299,2)," ",VLOOKUP($T$12,W304:X313,2)),""))&CHAR(10)&CHAR(10),
is also TRUE because text values are > numbers so AND(U12>0,T12>0) resolves to be TRUE (again highlight that part and you will see TRUE in the 'bubble') and that line does NOT concatenate the "P.S., " before the VLOOKUP result and is why you weren't getting that P.S. part before. Now you are getting the correct line T12=" " AND the incorrect line T12>0.
You can fix it by adding the check or if you never have 0 just replacing it with ISNUMBER(T12).
As for the difference between "" and " " let's think about a balloon that you take out of the bag that isn't inflated and the balloon after you inflate it. I would call both a balloon but they certainly aren't the same.
Another way to look at it is that don't you think" " is different than " "because the former has a lot of spaces while the latter is only 1 space so why wouldn't you think "" is different than " "?
As to your entry sentence...
A...the notes contained on sheet 01 - v2.22 and 03 - eABC response are only there for those who would see this post as initial guidance into the problem I was having. They will disappear once solutions are provided. Also it is important to note, this project is an internal document we will use to breakdown the viability of assets we are in negotiations on. It functions as a real time negotiating and tracking platform to be used when in phone conversations with potential sellers of commercial property. I have exhaustively scouted the CRM marketplace including Goldmine CRM, one that I developed and used successfully while the owner of both a real estate and mortgage brokerage in L.A. I wanted to find an out of the box solution to these types of issues but nothing even got close. Not even something as simple as,
1. Send outgoing email...action: move thread to a long term trickle stage until the recipient responds.
2. Upon response, move thread to a pause stage while we make the seller wait up to 3 days depending on where in the negotiating process we are.
3. Once we take off the pause and send our reply, they go back into the 30 day trickle stage and that timing rolls on and on until we buy. If the seller and I never align the trickle continues on and on or until the property is pulled from market.
Every CRM from free to $1,000s/mo. We're incapable of this. They could automate mail merges and the like, but incapable of what we need. I am attempting a manual version in Excel. We'll see if works out or needs some tweaks or, is destined to fail. I have no idea where this ends up. And most importantly to complete my response in this area, this is not for public consumption. Maybe an assistant, virtual or otherwise might be plugged intl to duplicate volume...we'll see about that...
I saw your comment about a large range taking up a lot of file size along with a notation "XE1048576". I am not understanding what that sequence is referencing.
It might reference a set aside range of rows beginning at A12:UU1500? Within these rows are an extension of all formulas used to drive future data entries that span the range A:UU in this sheet. Each property and owner's information for each property, calculations, etc. encompass 1 row. When this goes live I will add around 50-75 rows of data per day. Some will have mostly complete data entry and some where only a couple of cells contain values.
I have used a similar system for different purposes except that it started small and 20 or 30 rows were added as needed. In that case, the addition of rows might have been 5 rows a month so I could do that manually without worry about mis-handling the copy/paste. I believe pre-adding a larger chunk will be easier and more consistently performing than smaller increments despite the increased file size. The more often manual intervention is introduced the greater the likelihood of mistakes happening.
You said you were not clear on my problem. I will try to break it down differently than in the inserted note boxes.
I am responding from my mobile now. Will send this portion forward and work on better explaining the problem(s) I am attempting to solve from my home computer. I'll send something over a bit later.
Sorry for the elongated response...so much easier on the phone!
I saw your comment about a large range taking up a lot of file size along with a notation "XE1048576". I am not understanding what that sequence is referencing.***
If you press CTRL+END you will be at XE1048576. Which is the endpoint of UsedRange.
But it should be VP1501.