Visual Basic 1.0 first come out on DOS. It was very similiar to quick basic, and it had a "GUI" (Character based) that you could place forms, windows, command buttons, lists, etc. The nice thing was that you could then take the VB 1.0 for DOS app and load it up in VB 1.0 for Windows and it'd work. Although there was some minor issues with things being in a frame. Apparently, controls at coordinates 0,0 in a frame under DOS meant just inside the frame (OK, it's character based, so 1 character down, and 1 to the right), in windows, it meant right on top of the frame (And actually a bit left and up from being "inside"). So while it would run, it was pretty ugly, but 5 minutes later of re-placing the controls and you had an application that ran in both DOS and Windows (natively -- no DOS Box).
Maybe it's time the movie producers realized that they should distribute their movies themselves online? Then they could keep all the money, rather than only the 25% you suggest.
Stored procedures are BAD BAD BAD, I'm glad you have a hard time promoting those. Why?
You can't easily migrate to another database-vendor. Maybe you want to switch. Maybe you have to because of technical reasons. Maybe you have to because your company is being bought by another, which uses a different system and wants to maintain only one platform. Whatever the reason, your stored procedure is going to really, really hurt.
Heh, I'd have to completely disagree there. By using stored procedures exclusively in an application, you abstract the database inconsistancies from the application. If you want to replace the database (or run on multiple databases), then just call the new database's stored procedures passing the same parameters that you always have. It shouldn't require a change to the application, plus you get reduced network traffic, increased responsiveness, and decrease the load on the database.
Slashdot Mirror
Tool.
You should have gone to a better school. 100-93 Was an A 92-86 Was a B 85-80 Was a C 79-75 Was a D 74-below was an F
Visual Basic 1.0 first come out on DOS. It was very similiar to quick basic, and it had a "GUI" (Character based) that you could place forms, windows, command buttons, lists, etc. The nice thing was that you could then take the VB 1.0 for DOS app and load it up in VB 1.0 for Windows and it'd work. Although there was some minor issues with things being in a frame. Apparently, controls at coordinates 0,0 in a frame under DOS meant just inside the frame (OK, it's character based, so 1 character down, and 1 to the right), in windows, it meant right on top of the frame (And actually a bit left and up from being "inside"). So while it would run, it was pretty ugly, but 5 minutes later of re-placing the controls and you had an application that ran in both DOS and Windows (natively -- no DOS Box).
Maybe it's time the movie producers realized that they should distribute their movies themselves online? Then they could keep all the money, rather than only the 25% you suggest.
Don't blame the SQL Vendors, blame the SQL Standards which are always 5-7 years behind what the database vendors actually implement featurewise.