General discussion


Bitten off more than I can chew ??

By Bubsa ·
I have been a SQL DBA for about 4 years now not a very advanced one as we did not use stored procedures, database mirroring or any fancy stuff but good enough to get my job done for my role within the company. I was made redundant did nowt for a few months but have fallen into a new job as an IT Manager ...... now heres the tricky bit I am being employed to help update a old visual basic application that runs on a access database to new improved system to be written using visual studio 2008 and a sql2008 database. Even though I have NO programing experience, the old application does not look that complicated and with not many tables. The new application has to be web based.

My Employer knows that I have never used Visual Studio 2008. Though he would like to see the application ready in about four months. I have purchased a book from Amazon and have some CBT training DVDs also a developer started this project but left the company so I have some stuff to look at after I understand it first. I am quite good at reading from books and passing exams (Passed A+, Network+, I-Net+ and a few MCPs) all from reading without to much pratical exposure.

But Have I bitten off more than I can chew of is 4 months enough time to learn and develop a stock & quote system ? Any Tips ?

This conversation is currently closed to new comments.

Thread display: Collapse - | Expand +

All Comments

Collapse -

Possibly, there's a lot to learn

by Tony Hopkinson In reply to Bitten off more than I ca ...

Securing it for instance, using parameterised queries to evade sql injection attacks. https for secure sign on.
How rich you make it...

Start simple, get the 'home' page and login going. Figure out teh site structure, and set up the pages and the state variables you need to drive them from ach other.
LoginToken, user name.

Have a look at some similer apps on the interweb, see waht works waht doesn't then a lot og=f googling for how to and best practice.

The trick is to have something useful to show, whatvere you do they will probably want to change it anyway, so make it modular.

Best of luck.

Onec you know enough ask ome specific questions, there are plent of people on here who'll have an opinion worth noting.

Collapse -

It'll be a Steep Learning Curve

by OxonDev In reply to Bitten off more than I ca ...

...even if your employer expects you just to replicate the old application in a web environment. If your employer wants a mission critical application, you don't consider yourself a developer, and you can walk away from this, I would pass the buck toute suite.

Having said that, if the legacy app is truly simple, quick and dirty is good enough, and you've some free time... As Tony said, start simple. Work out what your data entities are, the legacy aplication processes, and see if you can find examples that model them. Some sort of work flow will help you ask others "how do you do this".

Good Luck.

Collapse -

If you're prepared to learn...

by SwissJon In reply to Bitten off more than I ca ... can do anything.. My concern is that during your time in the past 4 years, you didn't bother to poke around and learn more about what you were working with. This kinda suggests that you aren't particularly interested, but that's your problem, if you can find your interest, the rest should be fairly simple..

Access has an upsizer that will push the tables, views and data out to SQL for you, reasonably easy to do so long as there's no data corruption.. Believe me, if it's an access database that's just grown without anybody keeping an eye on things, 4 months might not be enough, even for an experienced developer.. ASP.NET is reasonably easy to get your head round for developing the fron end.. But there's a lot to learn..

Suggest you go on an SQL course.. Use that knowledge to push the data to SQL. Link the tables in Access, let the users trial that for a week while you go on an ASP.NET course, and then start to develop the front end. Only before you start, talk to the users and find out what they don't like, and try to program that out while you're at it.. Experience suggests that if you just try to replicate what people were seeing, they'll find fault when it's not EXACTLY the same, however, if you get rid of some of their gripes, they'll be more forgiving.

And don't try to learn until you've got your head round SQL.. You need to know how to extract the data before you learn how to present it

Related Discussions

Related Forums