Mongo
May 2nd, 2000, 11:09 AM
Well, you certainly have lots of moxy, but please be sure you aren’t trying to solve world hunger via the marketing hype of VB RAD, ADO, et al – building a productive, useful client/server app is a tall order. Is that polite enough warning to carefully consider knowing “enough to be dangerous?”
You have at least three major hurdles to cross: planning, design and implementation. In each, you want to be smart about your choices; make them Specific, Measurable, Achievable, Realistic, and Time Oriented. I know free advice is cheap and I’m a dope; so here are a few ideas, in no particular order, for your consideration.
Do your research now. Personally, I’m a fan of the software development lifecycle (SDLC) process, but that, like QB7, is generally considered a dated methodology. Bone-up on the VB programming conventions that your programmers at work use and follow them. Download a copy of “Microsoft Windows NT Server Migration Lab” at http://msdn.microsoft.com/workshop/server/migrlab/howto.asp and adapt its structure to what you intend producing. Make the time to learn to breathe chapters 3-7 of Sybase Unleashed (after using a bold marker to write “NEVER, NEVER!” over every mention of the alter table command). Get a dial-in connection to your server and build all but the gee-whiz GUI stuff server-side. Keep your sense of humor, this won't be a quick or easy task.
Your points are well taken Mongo and Thank You! I didn't mean to sound cocky or over confident......I certainly know I have months of work ahead of me.
I'm not sure however if you ever answered my question though. Is code I create to manipulate an access database going to work when I access a Sybase database? (yes / no)
My driver for wanting to use Access is that it would allow me to work on Learning Visual Basic 6.0 at home where I don't have access to Sybase. Will I be wasting my time?
I was just thinking it would be easier for me as a beginner to develop my tables and relationships in Access to understand the basics before I even attempt Sybase.
Anyway.....Thanks
Mongo
May 4th, 2000, 12:00 PM
If by "code to manipulate the database" you mean SQL, the answer is yes and no. How's that for wishy-washy?!? *smirk* (part of why I didn't answer you directly before). The SQL is similar, but different for each. So, yes, in a generic sense, you can use the silly code-builder thing in Access to create SQL that can work; while, no, in specific terms, it will be a redundant effort. Yes, as an exercise in designing a third degree black-belt normalized/de-normalized data structure; and no for building the specific referential integrity, binding and demand testing stuff. Yes, for doing small single-user tables (<50,000 records); and no, for larger multi-user tables.
I don't mean to preach. I encourage you to build your plan on paper first. Think n-tier. I apologize if I've over-reacted, you struck a nerve, er, well, may be I’ve just hit myself over the head too much… too often, as the wry story goes, a [fill-in-the-blank: PC/kiss-up team leader, manager, customer] shouts, "Start coding while I go get the specs!" End result being it’s not done, because it's not sexy, exciting or particularly fun; yet, there’s no limit to the gloom when months have passed and no end is in site and/or you have only a useless pile of garbage.
I believe it's more efficient for you to develop your database objects, intended rules and relations on paper. Then, later, coding from a well thought out, pre-approved, known series of positions, written down in a documented plan is easier, than coding on the fly into corners off the back of sticky gum wrappers.
Do you remember the Steve Martin routine where he’d wear faux American Indian garb and dance around? "Hiya, hiya, hiya. Hiya, hiya, hiya, hiya. [continued, ad nauseam] Hiya, hiya, hiya, little girl." *LOL* It occurred to me I’m doing my own rain-dance and it came to mind. Oh well, while I’m raining on your parade (and I mean that in a kidding sense), I have kicked myself in the head for not stressing that this adventure needs to be a team effort. If you don’t have one, start building it. Father, son, is a good start – though watch the corner-cutting, integrity’s important and business application with academic pricing can lead to less than praise… Ah, cross-check, I’m preachin’ – to the penalty box for me!
Hey, how about one of you master-types chiming in here to help toga?!?
I sense you don't feel I'm listening to your advise Mongo…..Not True!
You told me to get a copy of Sybase SQL Server 11 UNLEASHED….Done I have it right here.
You told me to Download a copy of "Microsoft Windows NT Server Migration Lab" at http://msdn.microsoft.com/workshop /server/migrlab/howto.asp ….. I have browsed through it and have book marked it.
You told me to get a dial-in connection to my Sybase server - In process, I brought the approval request form home today.
You been preaching that I need to Plan Plan Plan (Good Advise by the way!) and that's what I feel I am doing.
What I don't think you've heard though is that I haven't programmed in almost 10 years....and that was with QB 7.0
What I'm trying to sort out right now is my curriculum...
What software do I need. What do I spend my time learning.
With a little self disipline, stubbornness and help from this web site, I feel like I can get a handle on VB 6.0
Sybase scares the hell out of me! That UNLEASHED book is way over my head right now. Isn't there like a Sybase for Dummies book available? How do I start from zero knowledge
and pick up what I need to know? I guess that's why I was wondering about access....since I already know that a little bit. But it sounds like I might just confuse myself more than anything
As for team work and planning my database out on paper first.....that stuff will happen. I know that's very important from the last program I wrote....and it paid off! BTW....Do you know that I wrote that program almost 10 years ago (A DOS database application using random access files) and we're still using it everyday to enter in all our test data and generate test reports for our customers. Pretty sad huh! It's a dinosaur relative to the software available nowadays....but I'm still pretty proud of it! In fact we have 3 DOS programs I wrote that are still being used everyday. So much for patting myself on the back.....I got a tall order ahead of me!
Anyway...I have appreciated your advice and hope I can continue to ask for it....as well as other peoples help in here.
Well....I've babbled far too long. People are going to start refferring to this exchange as the Mongo & Toga Show....no wait...that's not right.. The Toga & Mongo Show! LOL Thanks!