Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Since I cut my teeth on Visual Basic (the resume says VB3-6 10+ years), I'll try actually answering your question with something other than "On Error Resume Next" sucks (which it does, but you'll find it all over the place, or you won't, which is worse). Here are some things you can do:</p> <ol> <li>When you take over a VB project, the hardest thing is usually just getting it to compile on your machine. This is often due to broken references to things that were installed on the original developer's machine but not on yours (a.k.a. "DLL Hell"). You can only hope the installers still exist somewhere, or if not you can always resort to dropping DLLs and OCXs into the system directory (remember to register them). Sometimes the DLL Hell comes from broken internal references. VB developers usually loved to divide applications up into as many different component projects as possible. Often many or all of your compatibility problems vanish when you just combine everything into the one damn project it should have been in the first place.</li> <li>Once everything compiles, you're 99% there. Most of the common problems mentioned in posts here are the kind of problems that manifest themselves in an application immediately. If the app you're inheriting is a simple, reliable app that's been humming along quietly all these years (it happened in VB), you're probably going to be fine.</li> <li>Once you have the app compiled and working from the IDE (I think that's what it was called back then), you can start experimenting with small changes here and there.</li> <li><strong>Post your problems here</strong>. It's fun to be reminded of the past.</li> </ol> <p>Regarding Visual Basic in general, I would say don't believe the anti-hype. It was a language that allowed good code or bad code, much like any other. And remember that all the awful VB programmers are now awful C# programmers.</p>
    singulars
    1. This table or related slice is empty.
    1. POPicking up a VB6 project for a non-VB6 guy
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USMusiGenesis
    1. USMusiGenesis
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COI don't entirely agree with this. VB is the only language I've ever worked with (with the possible exception of SQL) that had architectural limitations - largely due to its tight coupling with COM - that made it hard to write good code in.
      singulars
      1. PO
      1. USConcernedOfTunbridgeWells
    2. COVB 3 certainly had some architectural limitations (no classes - I have no idea how I did anything without classes).
      singulars
      1. PO
      1. USMusiGenesis
    3. CO+1 It's nice to see realistic comments about VB. It never was the "best," but it's also far from the worst.
      singulars
      1. PO
      1. USJeffK
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload