How did we write code without the Internet?
-
Yes, we had 200 lbs of reference manuals, and life was simpler. I just finished a whole bunch of googling to figure out how to bulk copy an archaic Access DBF file into SQL Server, using .NET 7. My comments in the code show some of the depth of the rabbit hole.
// Need to download the Microsoft Access Database Engine 2010 Redistributable for the 64 bit version of the Microsoft.Jet.OLEDB driver.
// Unless you already have the 32 bit version installed, you can't have both, so you would have to uninstall any 32 bit apps, in my case, Visio and FrontPage!
// This appears to work, from SO: use the provider to “Provider=Microsoft.ACE.OLEDB.12.0;” in connection string.
// But it doesn't because the DBF files are so old, so we're back to using Jet.OLEDB and building the importer app as a 32 bit (x86) app.
// And I finally can import the data!And yes, I still use FrontPage for article writing and I'll be damned if I'm going to uninstall it and Visio 2010 to install the 64 bit Jet drivers, so now my importer app is in x86 mode. And stunningly, the .NET
SqlBulkCopything is working perfectly.Latest Articles:
A Lightweight Thread Safe In-Memory Keyed Generic Cache Collection Service A Dynamic Where Implementation for Entity FrameworkNot only write code but all the information that's available on EVERYTHING, it's amazing what Mr.Google knows.
Give me coffee to change the things I can and wine for those I can not! PartsBin an Electronics Part Organizer - An updated version available! JaxCoder.com Latest Article: Simon Says, A Child's Game
-
Yes, we had 200 lbs of reference manuals, and life was simpler. I just finished a whole bunch of googling to figure out how to bulk copy an archaic Access DBF file into SQL Server, using .NET 7. My comments in the code show some of the depth of the rabbit hole.
// Need to download the Microsoft Access Database Engine 2010 Redistributable for the 64 bit version of the Microsoft.Jet.OLEDB driver.
// Unless you already have the 32 bit version installed, you can't have both, so you would have to uninstall any 32 bit apps, in my case, Visio and FrontPage!
// This appears to work, from SO: use the provider to “Provider=Microsoft.ACE.OLEDB.12.0;” in connection string.
// But it doesn't because the DBF files are so old, so we're back to using Jet.OLEDB and building the importer app as a 32 bit (x86) app.
// And I finally can import the data!And yes, I still use FrontPage for article writing and I'll be damned if I'm going to uninstall it and Visio 2010 to install the 64 bit Jet drivers, so now my importer app is in x86 mode. And stunningly, the .NET
SqlBulkCopything is working perfectly.Latest Articles:
A Lightweight Thread Safe In-Memory Keyed Generic Cache Collection Service A Dynamic Where Implementation for Entity FrameworkThis is one place where virtual machines really come in handy. It's such a shame that the IT gestapo where I work won't let me use VirtualBox (which is free) and refuse to give me a license for the sanctioned VM package.
Software Zen:
delete this; -
This is one place where virtual machines really come in handy. It's such a shame that the IT gestapo where I work won't let me use VirtualBox (which is free) and refuse to give me a license for the sanctioned VM package.
Software Zen:
delete this;Gary R. Wheeler wrote:
This is one place where virtual machines really come in handy.
:thumbsup::thumbsup::thumbsup::thumbsup:
Gary R. Wheeler wrote:
It's such a shame that the IT gestapo where I work won't let me use VirtualBox (which is free) and refuse to give me a license for the sanctioned VM package
I can relate to that too... sadly
M.D.V. ;) If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about? Help me to understand what I'm saying, and I'll explain it better to you Rating helpful answers is nice, but saying thanks can be even nicer.
-
I guess that you are not using the same mainboard, disk, keyboard and screen as you did in the 1900s. So what happened to that machine? Or, I suppose, those machines that you have replaced. Didn't you keep keep any of them for running old SW? (and for that sake: HW. I've got several pieces of hardware that cannot be moved to my current machine for lack of interface / bus.)
trønderen wrote:
Didn't you keep keep any of them for running old SW?
Yes, and several are still sitting in my shed. None earlier than W95, it would be amusing to fire up Windows 3.1. Or a DOS box. I wonder what happened to the PDP/11 that I cut my teeth on (not literally) when I was in 7th grade.
Latest Articles:
A Lightweight Thread Safe In-Memory Keyed Generic Cache Collection Service A Dynamic Where Implementation for Entity Framework -
Marc Clifton wrote:
And yes, I still use FrontPage for article writing
Noooooo.... Nooo Marc. My eyes. They're melting. Aaaaaggggggggggh. :wtf:
Jeremy Falcon
hahaha. It's still the best darn editor for split HTML and WYSIWYG editing, IMO.
Latest Articles:
A Lightweight Thread Safe In-Memory Keyed Generic Cache Collection Service A Dynamic Where Implementation for Entity Framework -
Yes, we had 200 lbs of reference manuals, and life was simpler. I just finished a whole bunch of googling to figure out how to bulk copy an archaic Access DBF file into SQL Server, using .NET 7. My comments in the code show some of the depth of the rabbit hole.
// Need to download the Microsoft Access Database Engine 2010 Redistributable for the 64 bit version of the Microsoft.Jet.OLEDB driver.
// Unless you already have the 32 bit version installed, you can't have both, so you would have to uninstall any 32 bit apps, in my case, Visio and FrontPage!
// This appears to work, from SO: use the provider to “Provider=Microsoft.ACE.OLEDB.12.0;” in connection string.
// But it doesn't because the DBF files are so old, so we're back to using Jet.OLEDB and building the importer app as a 32 bit (x86) app.
// And I finally can import the data!And yes, I still use FrontPage for article writing and I'll be damned if I'm going to uninstall it and Visio 2010 to install the 64 bit Jet drivers, so now my importer app is in x86 mode. And stunningly, the .NET
SqlBulkCopything is working perfectly.Latest Articles:
A Lightweight Thread Safe In-Memory Keyed Generic Cache Collection Service A Dynamic Where Implementation for Entity FrameworkI currently work with someone who's officially retired, but sticks around because his software is VB6 and dBase and nobody knows how that stuff works. He's currently converting everything to SQL Server, despite not knowing how SQL Server works (I don't know how he does it). After that I get to rewrite his software to .NET (he already ported two application to .NET Framework 2, obviously he doesn't know how that works either). Not particularly looking forward to inheriting that one :sigh:
Best, Sander Azure DevOps Succinctly (free eBook) Azure Serverless Succinctly (free eBook) Migrating Apps to the Cloud with Azure arrgh.js - Bringing LINQ to JavaScript
-
Yes, we had 200 lbs of reference manuals, and life was simpler. I just finished a whole bunch of googling to figure out how to bulk copy an archaic Access DBF file into SQL Server, using .NET 7. My comments in the code show some of the depth of the rabbit hole.
// Need to download the Microsoft Access Database Engine 2010 Redistributable for the 64 bit version of the Microsoft.Jet.OLEDB driver.
// Unless you already have the 32 bit version installed, you can't have both, so you would have to uninstall any 32 bit apps, in my case, Visio and FrontPage!
// This appears to work, from SO: use the provider to “Provider=Microsoft.ACE.OLEDB.12.0;” in connection string.
// But it doesn't because the DBF files are so old, so we're back to using Jet.OLEDB and building the importer app as a 32 bit (x86) app.
// And I finally can import the data!And yes, I still use FrontPage for article writing and I'll be damned if I'm going to uninstall it and Visio 2010 to install the 64 bit Jet drivers, so now my importer app is in x86 mode. And stunningly, the .NET
SqlBulkCopything is working perfectly.Latest Articles:
A Lightweight Thread Safe In-Memory Keyed Generic Cache Collection Service A Dynamic Where Implementation for Entity FrameworkMy turbo pascal 2.0 manual was one handy paperback pocketbook. It was all you needed. Try that with c#. They keep adding stuff, when are they gooing to remove a lot of fluff?
-
Yes, we had 200 lbs of reference manuals, and life was simpler. I just finished a whole bunch of googling to figure out how to bulk copy an archaic Access DBF file into SQL Server, using .NET 7. My comments in the code show some of the depth of the rabbit hole.
// Need to download the Microsoft Access Database Engine 2010 Redistributable for the 64 bit version of the Microsoft.Jet.OLEDB driver.
// Unless you already have the 32 bit version installed, you can't have both, so you would have to uninstall any 32 bit apps, in my case, Visio and FrontPage!
// This appears to work, from SO: use the provider to “Provider=Microsoft.ACE.OLEDB.12.0;” in connection string.
// But it doesn't because the DBF files are so old, so we're back to using Jet.OLEDB and building the importer app as a 32 bit (x86) app.
// And I finally can import the data!And yes, I still use FrontPage for article writing and I'll be damned if I'm going to uninstall it and Visio 2010 to install the 64 bit Jet drivers, so now my importer app is in x86 mode. And stunningly, the .NET
SqlBulkCopything is working perfectly.Latest Articles:
A Lightweight Thread Safe In-Memory Keyed Generic Cache Collection Service A Dynamic Where Implementation for Entity FrameworkWe wrote it much better back then. Now we have internet, we have to find out everything ourselves as nothing gets documented, go to code project and other sites to ask other users how things work. Before the internet, everything was properly documented, so we didn't need those forums. So the answer is that it is much harder now than it was before the internet.
-
Yes, we had 200 lbs of reference manuals, and life was simpler. I just finished a whole bunch of googling to figure out how to bulk copy an archaic Access DBF file into SQL Server, using .NET 7. My comments in the code show some of the depth of the rabbit hole.
// Need to download the Microsoft Access Database Engine 2010 Redistributable for the 64 bit version of the Microsoft.Jet.OLEDB driver.
// Unless you already have the 32 bit version installed, you can't have both, so you would have to uninstall any 32 bit apps, in my case, Visio and FrontPage!
// This appears to work, from SO: use the provider to “Provider=Microsoft.ACE.OLEDB.12.0;” in connection string.
// But it doesn't because the DBF files are so old, so we're back to using Jet.OLEDB and building the importer app as a 32 bit (x86) app.
// And I finally can import the data!And yes, I still use FrontPage for article writing and I'll be damned if I'm going to uninstall it and Visio 2010 to install the 64 bit Jet drivers, so now my importer app is in x86 mode. And stunningly, the .NET
SqlBulkCopything is working perfectly.Latest Articles:
A Lightweight Thread Safe In-Memory Keyed Generic Cache Collection Service A Dynamic Where Implementation for Entity FrameworkBack before the internet, I had more RAM in my brain, and memorized many things I don't bother to keep in RAM today. :) And there were many less constructs to have to keep in memory, unless you were doing assembly language. There were a lot less instructions for that as well, but I'm not good about remembering cryptic stuff. As others pointed out, we also had those marvelous things called reference books!
-
Yes, we had 200 lbs of reference manuals, and life was simpler. I just finished a whole bunch of googling to figure out how to bulk copy an archaic Access DBF file into SQL Server, using .NET 7. My comments in the code show some of the depth of the rabbit hole.
// Need to download the Microsoft Access Database Engine 2010 Redistributable for the 64 bit version of the Microsoft.Jet.OLEDB driver.
// Unless you already have the 32 bit version installed, you can't have both, so you would have to uninstall any 32 bit apps, in my case, Visio and FrontPage!
// This appears to work, from SO: use the provider to “Provider=Microsoft.ACE.OLEDB.12.0;” in connection string.
// But it doesn't because the DBF files are so old, so we're back to using Jet.OLEDB and building the importer app as a 32 bit (x86) app.
// And I finally can import the data!And yes, I still use FrontPage for article writing and I'll be damned if I'm going to uninstall it and Visio 2010 to install the 64 bit Jet drivers, so now my importer app is in x86 mode. And stunningly, the .NET
SqlBulkCopything is working perfectly.Latest Articles:
A Lightweight Thread Safe In-Memory Keyed Generic Cache Collection Service A Dynamic Where Implementation for Entity FrameworkLike you, I used a lot of manuals... That being said, from everything I have seen during my long career and my current involvement with my profession, I am coming to the conclusion that the Internet has made most things worse for all of us; especially how management treats us professionals and the way most companies now treat their customers. Combine this with all the criminality that is now ever present on the Internet and we have a "perfect storm" of dysfunction which is increasingly getting worse...
Steve Naidamast Sr. Software Engineer Black Falcon Software, Inc. blackfalconsoftware@outlook.com
-
hahaha. It's still the best darn editor for split HTML and WYSIWYG editing, IMO.
Latest Articles:
A Lightweight Thread Safe In-Memory Keyed Generic Cache Collection Service A Dynamic Where Implementation for Entity Framework -
Yes, we had 200 lbs of reference manuals, and life was simpler. I just finished a whole bunch of googling to figure out how to bulk copy an archaic Access DBF file into SQL Server, using .NET 7. My comments in the code show some of the depth of the rabbit hole.
// Need to download the Microsoft Access Database Engine 2010 Redistributable for the 64 bit version of the Microsoft.Jet.OLEDB driver.
// Unless you already have the 32 bit version installed, you can't have both, so you would have to uninstall any 32 bit apps, in my case, Visio and FrontPage!
// This appears to work, from SO: use the provider to “Provider=Microsoft.ACE.OLEDB.12.0;” in connection string.
// But it doesn't because the DBF files are so old, so we're back to using Jet.OLEDB and building the importer app as a 32 bit (x86) app.
// And I finally can import the data!And yes, I still use FrontPage for article writing and I'll be damned if I'm going to uninstall it and Visio 2010 to install the 64 bit Jet drivers, so now my importer app is in x86 mode. And stunningly, the .NET
SqlBulkCopything is working perfectly.Latest Articles:
A Lightweight Thread Safe In-Memory Keyed Generic Cache Collection Service A Dynamic Where Implementation for Entity FrameworkBooks! I've still got the first microcomputer/programming book I bought in 1978 (when I built my first computer). It's "the Z-80 microcomputer handbook" by William Barden Jr. It's where I learned the z80 architecture and how to program the computer I'd built. Had no real OS, just a simple monitor program called Zapple. It allowed dumping memory, peeking and poking memory, execute at a specified address and setting a breakpoint. There was no assembler so I was programming via the opcodes. Fun times.
-
Yes, we had 200 lbs of reference manuals, and life was simpler. I just finished a whole bunch of googling to figure out how to bulk copy an archaic Access DBF file into SQL Server, using .NET 7. My comments in the code show some of the depth of the rabbit hole.
// Need to download the Microsoft Access Database Engine 2010 Redistributable for the 64 bit version of the Microsoft.Jet.OLEDB driver.
// Unless you already have the 32 bit version installed, you can't have both, so you would have to uninstall any 32 bit apps, in my case, Visio and FrontPage!
// This appears to work, from SO: use the provider to “Provider=Microsoft.ACE.OLEDB.12.0;” in connection string.
// But it doesn't because the DBF files are so old, so we're back to using Jet.OLEDB and building the importer app as a 32 bit (x86) app.
// And I finally can import the data!And yes, I still use FrontPage for article writing and I'll be damned if I'm going to uninstall it and Visio 2010 to install the 64 bit Jet drivers, so now my importer app is in x86 mode. And stunningly, the .NET
SqlBulkCopything is working perfectly.Latest Articles:
A Lightweight Thread Safe In-Memory Keyed Generic Cache Collection Service A Dynamic Where Implementation for Entity FrameworkWell, in those days (when the Dead Sea was on the Critical List) "Google" was running to the library and hopefully they had the books that answered your question. You would ask the Librarian or if you knew how to read the Dewey Decimal System and the card index, you could find the answers yourself.
-
Yes, we had 200 lbs of reference manuals, and life was simpler. I just finished a whole bunch of googling to figure out how to bulk copy an archaic Access DBF file into SQL Server, using .NET 7. My comments in the code show some of the depth of the rabbit hole.
// Need to download the Microsoft Access Database Engine 2010 Redistributable for the 64 bit version of the Microsoft.Jet.OLEDB driver.
// Unless you already have the 32 bit version installed, you can't have both, so you would have to uninstall any 32 bit apps, in my case, Visio and FrontPage!
// This appears to work, from SO: use the provider to “Provider=Microsoft.ACE.OLEDB.12.0;” in connection string.
// But it doesn't because the DBF files are so old, so we're back to using Jet.OLEDB and building the importer app as a 32 bit (x86) app.
// And I finally can import the data!And yes, I still use FrontPage for article writing and I'll be damned if I'm going to uninstall it and Visio 2010 to install the 64 bit Jet drivers, so now my importer app is in x86 mode. And stunningly, the .NET
SqlBulkCopything is working perfectly.Latest Articles:
A Lightweight Thread Safe In-Memory Keyed Generic Cache Collection Service A Dynamic Where Implementation for Entity FrameworkIBM operating system source code on microfiche. The holy grail (at the time).
"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
-
My turbo pascal 2.0 manual was one handy paperback pocketbook. It was all you needed. Try that with c#. They keep adding stuff, when are they gooing to remove a lot of fluff?
Kees van Sighem wrote:
when are they gooing to remove a lot of fluff?
Hopefully not so soon, I cant get up-to-date to the last shiny ways and I am mostly using the old fashioned things.
M.D.V. ;) If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about? Help me to understand what I'm saying, and I'll explain it better to you Rating helpful answers is nice, but saying thanks can be even nicer.
-
This is one place where virtual machines really come in handy. It's such a shame that the IT gestapo where I work won't let me use VirtualBox (which is free) and refuse to give me a license for the sanctioned VM package.
Software Zen:
delete this; -
Yes, we had 200 lbs of reference manuals, and life was simpler. I just finished a whole bunch of googling to figure out how to bulk copy an archaic Access DBF file into SQL Server, using .NET 7. My comments in the code show some of the depth of the rabbit hole.
// Need to download the Microsoft Access Database Engine 2010 Redistributable for the 64 bit version of the Microsoft.Jet.OLEDB driver.
// Unless you already have the 32 bit version installed, you can't have both, so you would have to uninstall any 32 bit apps, in my case, Visio and FrontPage!
// This appears to work, from SO: use the provider to “Provider=Microsoft.ACE.OLEDB.12.0;” in connection string.
// But it doesn't because the DBF files are so old, so we're back to using Jet.OLEDB and building the importer app as a 32 bit (x86) app.
// And I finally can import the data!And yes, I still use FrontPage for article writing and I'll be damned if I'm going to uninstall it and Visio 2010 to install the 64 bit Jet drivers, so now my importer app is in x86 mode. And stunningly, the .NET
SqlBulkCopything is working perfectly.Latest Articles:
A Lightweight Thread Safe In-Memory Keyed Generic Cache Collection Service A Dynamic Where Implementation for Entity Framework -
Yes, we had 200 lbs of reference manuals, and life was simpler. I just finished a whole bunch of googling to figure out how to bulk copy an archaic Access DBF file into SQL Server, using .NET 7. My comments in the code show some of the depth of the rabbit hole.
// Need to download the Microsoft Access Database Engine 2010 Redistributable for the 64 bit version of the Microsoft.Jet.OLEDB driver.
// Unless you already have the 32 bit version installed, you can't have both, so you would have to uninstall any 32 bit apps, in my case, Visio and FrontPage!
// This appears to work, from SO: use the provider to “Provider=Microsoft.ACE.OLEDB.12.0;” in connection string.
// But it doesn't because the DBF files are so old, so we're back to using Jet.OLEDB and building the importer app as a 32 bit (x86) app.
// And I finally can import the data!And yes, I still use FrontPage for article writing and I'll be damned if I'm going to uninstall it and Visio 2010 to install the 64 bit Jet drivers, so now my importer app is in x86 mode. And stunningly, the .NET
SqlBulkCopything is working perfectly.Latest Articles:
A Lightweight Thread Safe In-Memory Keyed Generic Cache Collection Service A Dynamic Where Implementation for Entity Framework -
I currently work with someone who's officially retired, but sticks around because his software is VB6 and dBase and nobody knows how that stuff works. He's currently converting everything to SQL Server, despite not knowing how SQL Server works (I don't know how he does it). After that I get to rewrite his software to .NET (he already ported two application to .NET Framework 2, obviously he doesn't know how that works either). Not particularly looking forward to inheriting that one :sigh:
Best, Sander Azure DevOps Succinctly (free eBook) Azure Serverless Succinctly (free eBook) Migrating Apps to the Cloud with Azure arrgh.js - Bringing LINQ to JavaScript
-
We wrote it much better back then. Now we have internet, we have to find out everything ourselves as nothing gets documented, go to code project and other sites to ask other users how things work. Before the internet, everything was properly documented, so we didn't need those forums. So the answer is that it is much harder now than it was before the internet.
