Reformed access user needs advise for future

Collapse
This topic is closed.
X
X
Collapse
 
  • Page of 1
  • Time
  • Show
Clear All
new posts
Previous template Next
  • John
    #1

    Reformed access user needs advise for future

    Hi

    Many a times I have been told off here for asking question on a backend
    other than sql sever. So I have finally seen the light and have decided to
    take up my next project with sql server backend (vb.net front). So here is
    my question;

    What are the recommended db development guidelines to achieve both a) a good
    user experience of being able to scroll to any record using record
    navigation buttons and b) the db efficiency requirement of not loading too
    many records in dataset at one time. If there is such a strategy to which
    many agree then there should be a sample code app somewhere. It would help
    me enormously to see the guts of an actual well written db app - no matter
    how trivial as long as it covers the necessary detail - instead of advise
    like don't do this or that without the coding specifics.

    So here is a chance for the worthy to lead a recent convert (albeit
    reluctant due to self deficiency on sql server side).

    Thanks

    Regards



    Tags: None
    • Cor Ligthert[MVP]
      #2
      Re: Reformed access user needs advise for future

      John,

      In my idea is the answer is simple. Create DataSets which contains all
      information from topic as you need it.

      Let say a sport club (I never used this, so it is an amateur club).
      Then you have in that
      The general information of a team
      The names of the players
      There rooster of playing
      The places the players live
      etc. etc.

      Make your relation to that. In fact try to create datasets that has all the
      information as you need it. Don't try to make by instance a dataset of
      persons, you mostly need only some of them. If you want to create a report
      of all players in your club you can forever access the datatables direct
      (this is short said because it is not as easy as I write here).

      Just my idea

      Cor



      "John" <John@nospam.in fovis.co.ukschr eef in bericht
      news:uhs$NHdaIH A.4880@TK2MSFTN GP03.phx.gbl...
      Hi
      >
      Many a times I have been told off here for asking question on a backend
      other than sql sever. So I have finally seen the light and have decided to
      take up my next project with sql server backend (vb.net front). So here is
      my question;
      >
      What are the recommended db development guidelines to achieve both a) a
      good user experience of being able to scroll to any record using record
      navigation buttons and b) the db efficiency requirement of not loading too
      many records in dataset at one time. If there is such a strategy to which
      many agree then there should be a sample code app somewhere. It would help
      me enormously to see the guts of an actual well written db app - no matter
      how trivial as long as it covers the necessary detail - instead of advise
      like don't do this or that without the coding specifics.
      >
      So here is a chance for the worthy to lead a recent convert (albeit
      reluctant due to self deficiency on sql server side).
      >
      Thanks
      >
      Regards
      >
      >
      >

        Comment

        • Spam Catcher
          #3
          Re: Reformed access user needs advise for future

          "Cor Ligthert[MVP]" <notmyfirstname @planet.nlwrote in
          news:9F67DE33-0D89-4706-8D8C-6D127D0485DC@mi crosoft.com:
          In my idea is the answer is simple. Create DataSets which contains all
          information from topic as you need it.
          >
          Let say a sport club (I never used this, so it is an amateur club).
          Then you have in that
          The general information of a team
          The names of the players
          There rooster of playing
          The places the players live
          etc. etc.
          >
          Make your relation to that. In fact try to create datasets that has
          all the information as you need it. Don't try to make by instance a
          dataset of persons, you mostly need only some of them. If you want to
          create a report of all players in your club you can forever access the
          datatables direct (this is short said because it is not as easy as I
          write here).
          I prefer to use a real OR mapping tool such as LLBLGen Pro. Much more
          polished than using datasets.

          --
          spamhoneypot@ro gers.com (Do not e-mail)

            Comment

            • Spam Catcher
              #4
              Re: Reformed access user needs advise for future

              "Michel Posseth [MCP]" <MSDN@posseth.c omwrote in
              news:uMVGA#vaIH A.1168@TK2MSFTN GP02.phx.gbl:
              I do it with custom code ,, made a data pager control with the superb
              sql server 2005 T-SQL syntax for paging this was pretty easy
              just do not like third party controls at all , i make everything
              myself if possible
              That's called "Not Invented Here Syndrome" - sometimes its worth weighing
              3rd party products to see if there is any value in using it. Sometimes
              there is, sometimes there isn't.

              --
              spamhoneypot@ro gers.com (Do not e-mail)

                Comment

                Previous template Next
                Working...