Re: Working with Sheridan Grid

From: Vlad (vovan.c_at_verizon.net)
Date: 03/17/04 

Date: Wed, 17 Mar 2004 08:52:18 -0500

I agree 100%. But the application I'm working on now is a pretty big and
complex. Current requirement is to move it from Access to SQL Server as
quick as possible. First step is to move data to SQL Server and make links
from Access to SQL Server. It will allow to start to use SQL Server with
minimal rewriting of the VB code. Then module by module will be rewritten in
order to work with SQL Server directly.
So far I did not see any serious problems with Sheridan Grid. So, if I will
replace this control with native MS control, it will be done in future only,
when I have the time.
Now I'm just looking for the fastest ways to switch to SQL Server
Thank you
Vlad

"Bonj" <anonymous@discussions.microsoft.com> wrote in message
news:2305E035-3D94-4C7E-937E-E6FA7631A346@microsoft.com...
> 3rd party grid/databound controls are poor, for the following reasons:
>
> a) They are not as controllable as the right combination of your own
controls and code, so no matter how rich in functionality the 3rd party
control is, you will never get it looking just the way you envisaged at the
outset.
>
> b) They are often built by poor programmers, possibly less experienced and
skilled than you are. They are intended to make profit, not to give you a
great application. As such, they are often rushed off and built in a very
slapdash way and contain lots of bugs - as long as they are generic and
vaguely work, they will get released.
>
> c) Support for 3rd party databound controls is often very poor or
non-existent, and source code is not often made available.
>
> d) They make you look lazy / incompetent like you can't program a data
report yourself.
>
> Much better to use your own combination of custom controls and/or VB
controls such as listbox, listview (MS windows common controls), textbox,
etc. to give your application a polished look that you can be proud that
you've built yourself the way YOU want it.

Relevant Pages

  • Re: ACCESS PROJECT, MS GRAPH, STORED PROCEDURE
    ... If the names of the parameters to the stored procedure HAPPEN to coincide ... with the name of either controls on your forms or fields in the forms ... > The problem apears because there is no Input Parameters property on the MS> Graph... ... > Is there any similar easy, intuitive, user-friendly substitute for Access> front-end for SQL Server? ...
    (microsoft.public.sqlserver.programming)
  • Re: newbie question
    ... In my opinion is it the best book for Newbie's for ADONET and SQL Server I ... you can still lock rows on the server if that's what you really ... I did some database programming in the past and I always used ... One facility that offered by these controls and I ...
    (microsoft.public.dotnet.framework.adonet)
  • Re: Working with Sheridan Grid
    ... "Vlad" wrote in message ... First step is to move data to SQL Server and make links ... (not counting download time... ... Obtaining the free ComponentOne ActiveX controls ...
    (microsoft.public.vb.general.discussion)
  • Changes in SQL tables and databinding
    ... I had a SQL server 2005 table in which I noticed I mispelled a column name. ... table adapter to a datagridview no longer recognized the changed column name ... related to databinding controls in the UI when a change is brought to the ...
    (microsoft.public.dotnet.languages.vb)
  • Re: Creating a control in Class1 ... and showing it in Class2 (winform)
    ... you have a dynamic GUI that must be built at runtime. ... my sundae" and that causes certain controls to be placed on the second ... label and so on have to be created at runtime. ...
    (microsoft.public.dotnet.languages.csharp)