|
It might fulfil the stated requirements, but the first time the Sr. Partner uses the report, the OP will be called on the carpet and told not to be such a smartass.
The OP will now have to do the work properly.
Freedom is the freedom to say that two plus two make four. If that is granted, all else follows.
-- 6079 Smith W.
|
|
|
|
|
Daniel Pfeffer wrote: the OP will be called on the carpet and told not to be such a smartass.
 You must know my colleague! If I'm not accused of it at least twice daily, I'm being too nice!
"Go forth into the source" - Neal Morse
"Hope is contagious"
|
|
|
|
|
In situations like you have, we would break out the data into 2 or more rows/lines (for both column headers and data). The columns would be offset from the previous row/line to improve readability and everything is left/right justified.
For example,
First Name
<\t> Last Name
James
<\t> Smith
----------------------------------------------------------------------
The font can remain the same for both rows/lines. You could also put a line between the different data points.
It will add complexity to the process in needing to report 2 or more rows/lines to output all of the data but it can be done.
This is not out of the norm. There can be reports that have as many as 3-5 lines for each data row in reports.
|
|
|
|
|
I've been sort of noticing it taking a long time for an item to show in Yahoo mail.
Today, however, I got some pretty good confirmation: and email forward that split to two targets, yahoo and another email box: the yahoo mail arrived about 30 minutes later.
For two concurrent mailings - not a one-off event.
Anyone else see this?
| Ravings en masse^ |
|---|
| "The difference between genius and stupidity is that genius has its limits." - Albert Einstein | | "If you are searching for perfection in others, then you seek disappointment. If you seek perfection in yourself, then you will find failure." - Balboos HaGadol Mar 2010 |
|
|
|
|
|
My wife uses a Yahoo mail account and we've seen that kind of behavior quite often. Just last week trying to get confirmation email it took a long time.
|
|
|
|
|
I have not had any issues. I have the mobile app installed and I get the emails come through fairly promptly (and from a variety of sources too).
I'm UK based through, so it could make a difference.
|
|
|
|
|
Is it possible to write a MFC application targeting Windows XP?
I have Visual Studio 2019 enterprise version. I have a legacy software still running on Windows XP, but it needs a utility software to prepare some data.
diligent hands rule....
|
|
|
|
|
IIRC, it's impossible in VS 2019.
VS 2017 has an XP target. If you meet the conditions for the target audience (work for yourself or for a company with 5 or fewer programmers and under a certain level of revenue), you can download VS 2017 Community Edition and use that. Otherwise, you'll have to spring for the Pro edition.
VS 2017 and 2019 may be installed side-by-side.
Freedom is the freedom to say that two plus two make four. If that is granted, all else follows.
-- 6079 Smith W.
modified 19-Aug-21 13:37pm.
|
|
|
|
|
I do have Visual Studio 2017 version on my laptop.
do I need to deploy any C++ runtime files?
diligent hands rule....
|
|
|
|
|
Not if you statically link -- 
This was an attempt at Software-Dev-Humor.
Most people do not find me funny.
|
|
|
|
|
You have to ensure that the XP target is installed. Otherwise, I assume that if you use dynamic linking you will have to include the appropriate runtime DLLs in your installation package, If you use static linking, you will need to distribute only your executable and any DLLs that are part of your project.
You may distribute the XP runtime DLLs on the same basis that you distribute runtime DLLs for applications targeted at later Windows versions. Note that unless it does something special with the hardware, a program targeted for XP should run on any later version of Windows as well.
Freedom is the freedom to say that two plus two make four. If that is granted, all else follows.
-- 6079 Smith W.
|
|
|
|
|
I got it...
diligent hands rule....
|
|
|
|
|
Daniel Pfeffer wrote: IIRC, it's impossible in VS 2019.
Not quite - you can install the VS2017 (v141) toolset in VS2019, together with the (now Deprecated) XP support MFC libraries for that toolset.
Bit more convoluted, but it is still possible...
Java, Basic, who cares - it's all a bunch of tree-hugging hippy cr*p
|
|
|
|
|
Yes, you can do this, but you still need to get VS2017 from somewhere...
Freedom is the freedom to say that two plus two make four. If that is granted, all else follows.
-- 6079 Smith W.
|
|
|
|
|
No, you don't - the VS2017 toolset, including XP & MFC bits are part of the VS2019 installer.
Hit the 'Modify' button in the VS2019 installer, select 'Individual Components' and search for 'v141'. It shows you all the VS2017 compiler & linker components you can install as part of VS2019.
Java, Basic, who cares - it's all a bunch of tree-hugging hippy cr*p
|
|
|
|
|
OK, I never noticed that. My bad... 
Freedom is the freedom to say that two plus two make four. If that is granted, all else follows.
-- 6079 Smith W.
|
|
|
|
|
Man you made my day. Now I can recompile the old sdl library without worry (yeah I know Windows 10 doesn't allow direct video memory access, but other stuff still works)
|
|
|
|
|
You need older dev tools. pm me.
Charlie Gilley
<italic>Stuck in a dysfunctional matrix from which I must escape...
"Where liberty dwells, there is my country." B. Franklin, 1783
“They who can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety.” BF, 1759
|
|
|
|
|
what kind of older tools do you recommend?
diligent hands rule....
|
|
|
|
|
As others have said, you have two issues: the correct SDK and a not to new IDE. I support legacy apps dating from 2005. The dev tools will only run under Xp, so I have a VM dating that far back.
I live in the embedded world. About 2010, Microsoft development went insane. They decided to abandon WinCE alienating a lot of people. A few years later, therapy helped them realize that the IoT (embedded) was going to be a big player, so they tried to get righteous. The issue is that the tool set got really flakey for supporting things. My point - choose the IDE wisely. On my Xp machine, I use VS2008 Pro. This is the last tool I can use for WinCE/WEC7 development. But that's my problem. If you're just doing a desktop app, you might get away with something newer.
I do recommend a VM.
Charlie Gilley
<italic>Stuck in a dysfunctional matrix from which I must escape...
"Where liberty dwells, there is my country." B. Franklin, 1783
“They who can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety.” BF, 1759
|
|
|
|
|
I have a legacy Windows XP machine. I have Visual Studio 2005 too.
diligent hands rule....
|
|
|
|
|
You should be good then. Just install the last SDK Microsoft released for Xp.
Charlie Gilley
<italic>Stuck in a dysfunctional matrix from which I must escape...
"Where liberty dwells, there is my country." B. Franklin, 1783
“They who can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety.” BF, 1759
|
|
|
|
|
i find that "Windows Server 2003 R2 Platform SDK" in .iso format works very good with anything from windows xp to windows 10, though "Windows Server 2003 SP1 Platform SDK" is also a popular option.
i would go with the former.
|
|
|
|
|
Anyone know how to remove the stupid "structure lines" from VS2019?
The horizontal dotted lines in this Screenshot
I've turned off "View Whitespace" and "Show Structure Guide Lines" in Tools => Options => Text Editor.
If it's not broken, fix it until it is.
Everything makes sense in someone's mind.
Ya can't fix stupid.
|
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
