By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
455,592 Members | 1,626 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 455,592 IT Pros & Developers. It's quick & easy.

guidelines for developing an application

P: n/a
Hi There,

I am about to develop a windows application. I was wondering if there is
any set of general guidelines I should be following when developing a
windows application? Is there a preference of writing SQL queries within the
application rather than Stored Procedures?

Please help

Thanks

Vivek
Nov 21 '05 #1
Share this Question
Share on Google+
4 Replies


P: n/a
Vivek,

What sort of guidelines are you referring to? If you are talking about
coding standards then I personally believe that it should be up to the
developer to come up with their own. If you are developing the project on
your own then so long as you can code the application in such a way that if
you were to come back to the project later you can understand what is going
on, then that should be fine.

If you are developing in a team it is probably best to have a meeting with
the other developers and come up with some coding standards between
yourselves that everybody is happy with and get them documented.

As for writing SQL queries, wherever possible I would try to write them as
stored procedures as this would make your code easier to maintain.

Hope this helps?

Kevin

"Vivek Sharma" wrote:
Hi There,

I am about to develop a windows application. I was wondering if there is
any set of general guidelines I should be following when developing a
windows application? Is there a preference of writing SQL queries within the
application rather than Stored Procedures?

Please help

Thanks

Vivek

Nov 21 '05 #2

P: n/a
Vivek,

The freedom of a programlanguage is that it let yourself decide what you can
take.

When you make a program than good sense, readability, and with that good
maintanability should be in my opinion your first guideline. Where is OOP
perfectly for.

The advance from a stored procedure above non stored procedure is not much.
In the current SQL server version you can solve a security problem by using
a stored procedure while there is a very little bit less datatransfer
needed.

In my opinion is it good first to use text commands and when your programma
is running create stored procedures from that. The change in a VBNet program
is almost only one statement per procedure.

Just my thought,

Cor
Nov 21 '05 #3

P: n/a
Hi,

Thanks a lot for your opinion. I appreciate your feedback. I am quite clear whatI want to achieve now.

Cor Question for you....

Could you please elaborate on this

The advance from a stored procedure above non stored procedure is not much.
In the current SQL server version you can solve a security problem by using
a stored procedure while there is a very little bit less datatransfer
needed.

In my opinion is it good first to use text commands and when your programma
is running create stored procedures from that. The change in a VBNet program
is almost only one statement per procedure.

I could not understand what you are trying to convey.

Lastly, i understand that I am going to have a role based security in my application. At the same time I want to develop a flexibility that allows users to create customised fields and forms. Can you please guide how can I achieve this?

Thanks again

Vivek
"Vivek Sharma" <jo*******@news.com> wrote in message news:eU*************@TK2MSFTNGP15.phx.gbl...
Hi There,

I am about to develop a windows application. I was wondering if there is
any set of general guidelines I should be following when developing a
windows application? Is there a preference of writing SQL queries within the
application rather than Stored Procedures?

Please help

Thanks

Vivek

Nov 21 '05 #4

P: n/a
Vivek,
In my opinion is it good first to use text commands and when your programma
is running create stored procedures from that. The change in a VBNet
program
is almost only one statement per procedure. I could not understand what you are trying to convey.
When I have made a new stored procedure I have to check on two places when
there is a SQL exception. When I first make it in my program I have to check
it only on one place when that exception is trowhed. That is all.
Lastly, i understand that I am going to have a role based security in my
application. At >the same time I want to develop a flexibility that
allows users to create customised >fields and forms. Can you please guide
how can I achieve this?


I almost never answer any security questions. I have the idea that when I
write it here, I can for the same write it as helptext on every program I
make for the guys who want to hack it.

Cor

Nov 21 '05 #5

This discussion thread is closed

Replies have been disabled for this discussion.