|
|
Pull out
sketch DRAW
first - letter A
learner L
to start with WITH
WITHDRAWAL
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony
"Common sense is so rare these days, it should be classified as a super power" - Random T-shirt
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
I think the hyphen would throw people off 
In a closed society where everybody's guilty, the only crime is getting caught. In a world of thieves, the only final sin is stupidity. - Hunter S Thompson - RIP
|
|
|
|
|
That's what punctuation is there for! 
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony
"Common sense is so rare these days, it should be classified as a super power" - Random T-shirt
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
I'm keen to guess. Does someone with a learner's permit in the UK have an "L" decal on their car?
|
|
|
|
|
Yep, and Hong Kong, India, Ireland, parts of Canadia, Israel, Malaysia, Spain, Oz, NZ, Switzerland, Poland, parts of the USA, ... loads of places!
In Wales, we have a Red 'L' for Learner, Green 'L' for recently passed, Green 'D' for "Disqualified", and Red 'D' for "Drunk"*
* That's a lie: the D is "Dysgwr", the Welsh for "Learner" but you wouldn't know that from the way they drive ... 
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony
"Common sense is so rare these days, it should be classified as a super power" - Random T-shirt
AntiTwitter: @DalekDave is now a follower!
modified yesterday.
|
|
|
|
|
Not in Minnesota USA anyway. Some families add a rear window sticker stating that there is a Student Driver - but this isn't required by law.
|
|
|
|
|
Nice clue! I even solved it - after I spent a fruitless half hour going down the rabbit hole pulling "out" from "outline" (another synonym of sketch) and getting nowhere. After re-reading the clue I saw "withdraw" as a definition of pull out. I easily got the A from first-letter but was unsure of L for learner, but withdrawal was too good a fit so I checked my guess against your solution. The "-" didn't throw me off, but I was so sure I was cleverly onto something with "outline"!
|
|
|
|
|
You should have posted! 
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony
"Common sense is so rare these days, it should be classified as a super power" - Random T-shirt
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
I had just solved it moments before my last post. I wasn't awake when the game was live. But I still work on them every day once I am. 
|
|
|
|
|
Good man 
In a closed society where everybody's guilty, the only crime is getting caught. In a world of thieves, the only final sin is stupidity. - Hunter S Thompson - RIP
|
|
|
|
|
A while back I asked for a Crystal Reports alternative (unrelated to the question below): The Lounge[^]
I got some very good responses from all of you.
Their reporting tool works on the web and in the cloud in .NET 5+ applications, which was kind of a requirement.
With that requirement in mind (and a few others), combit List&Label, Progress/Telerik and DevExpress made the shortlist.
Ultimately, I decided to go with DevExpress because it got a lot of good reviews, it's probably the most well-known tool in the list and their support is great (as is my experience with DevExpress).
I don't need it yet, but I told my client about it and we'll probably implement it later this year (after at least phase 1 of the project).
Thanks for the tips everyone 
|
|
|
|
|
Thanks for the update/summary.
|
|
|
|
|
I've used DevExpress. I find wiring report fields, bands, header, footers, etc. "fatiguing". One request was to add comments at report "preview" time. That was fun.
Unless you have a "lot" of canned reports, creating custom reports in UWP / WPF might be easier.
Related story: I needed a "monitor" screen for my app; 6 topics / tabs; many fields. I'd have some 20 fields going until I decided to use a single textbox per page, with wrapping, spaced the columns etc. using a stringbuilder; looks great (Consolas). Knocked off the other pages in little time more. Runs at 24 fps with no flicker.
"Before entering on an understanding, I have meditated for a long time, and have foreseen what might happen. It is not genius which reveals to me suddenly, secretly, what I have to say or to do in a circumstance unexpected by other people; it is reflection, it is meditation." - Napoleon I
|
|
|
|
|
What the title says.
For most people this (hopefully) happened some twenty years ago, but I'm going to inherit a lot of VB6 applications, some even still work with a dBase database.
The programmer is going into retirement and this (reasonably large) company needs someone to take care of their software.
Our (and their) first priority is getting off of dBase, the current programmer already started working on that.
Next we'll need to move VB6 to .NET (Framework, probably).
I know there used to be converter tools around, but I've heard bad things about them.
They're usually not worth the effort.
Ideally, I'd rather just rewrite everything to web-based and cloud-ready .NET 6 applications, but I don't think we'll have the time nor money.
Any tips (other than "RUN!")?
|
|
|
|
|
As someone who had to do this for a couple of clients, I can definitely say stay away from the conversion tools... they do not work!
If this software is critical to the company's business, I think you will have no option but to rewrite. Just hope that the current version works as is while you do that.
One thing I tried doing was to keep the UI same (or as similar as possible) so that users do not have to be re-trained a lot.
Happiness will never come to those who fail to appreciate what they already have. -Anon
|
|
|
|
|
It's a while since I had to, but the conversion tool with Vis Studio 2003 worked fine for me, I copied the UI in VB.Net was told to make it as close as I could 'convert the old one, that worked' only had rough code behind buttons converted it and it worked (then I ran).
|
|
|
|
|
So you want to go from VB6 to VB.NET? If you want to go from VB.NET to C# there is a host of problems which I encountered frequently... Have to do lots of things manually, even with code I wrote myself 
|
|
|
|
|
|
The problem is VB.NET is your target. VB.NET is not getting any new features. There was a time when MS said they were developing VB.NET and C# side-by-side, with the same features between the two. That has since been killed. VB.NET is going to "wither on the vine" without new features.
I'm going to say your best bet is to rewrite from scratch in C# instead.
|
|
|
|
|
It's safe to assume that people are not mentally challenged, and this is the first option that springs to their mind. But verry often, the time, resources and/or management's grasp of reality (or lack of) are preventing from going this path. Especially, when the purpose of the whole thing is just a small change in the current system.
Advertise here – minimum three posts per day are guaranteed.
|
|
|
|
|
Dude, all I said was moving to VB.NET isn't really a good choice because of its limited lifetime. If a conversion to .NET (anything) was going to happen, a more appropriate target would be C#.
|
|
|
|
|
Appropriate, sure. I am one that totally agrees with you as I once had to deal with a pile of VB6 and it is no fun at all.
As for getting signoff or access to resources or getting people to actually want to be forward thinking that are the final decision makers? This is a completely different issue and the bigger the company, expect the least ideal option being selected. And no it won't make sense. And yes, you will be frustrated greatly.
|
|
|
|
|
There is no doubt that C# is a solid move, provided that is in your skillset. If not vb.net is not going away as fast as everyone says. It was supposed to be gone in 2010,2015, 2019, 2022 and there are still MANY that use it. I have a friend who converted all of his work to C# and started his own business and nearly all the work he does is vb.net, not conversions. just vb. So until everyone makes the switch it will exist and probably till the end of my lifetime.
|
|
|
|
|
Is VB.NET the target? The OP isn't clear regarding that, although his statement can be taken that way. The wording indicates .NET Framework, not a newer version.
That said, I agree, C# is a better choice for the reasons you stated. At the time, VB.NET was a panacea for the extensive VB community, but as time has passed, so has the need for VB.NET, and MS has done less and less with it.
I'd target Framework 4.8.1 instead of a CORE release.
Why? Lifecycle. Framework has a lifespan as long as Windows contains it, which is 2029 for Win10, and I'm haven't checked for Win11.
Even versions (v6, v8) of CORE have a 3 year lifespan, while odd versions (v7) have an 18 month lifespan. That places an excessive burden on IT to update applications for which there is no business reason to update.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
