Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Code Project
CODE PROJECT For Those Who Code
  • Home
  • Articles
  • FAQ
Community
  1. Home
  2. General Programming
  3. Visual Basic
  4. Data Table or Business Object

Data Table or Business Object

Scheduled Pinned Locked Moved Visual Basic
databasebusinesssalesxmlhelp
1 Posts 1 Posters 0 Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • F Offline
    F Offline
    Fawxes
    wrote on last edited by
    #1

    I'm a novice at code writing (newbie is something my kids would call it) and need some advice. I need to write some code that enables me to access and manipulate data from a database object. This code has to validate the data away from the database. I would personally like to use an object that has methods that read and write to the database and properties that manage validation. This would make life easier when using the properties or field values with other objects. The problem with business objects is the time it takes to create the object. If I want to run a datagrid based on a collection of business objects it takes too long to create the object collection (for example sales orders). Linking the datagrid to a dataview and using a datatable to hold the values is far quicker. The business objects method appears to provide a better method of creating sales orders without access to the database using a localised copy of any necessary data (part codes, etc). One other point, the database is provided by a third party and I'm writing an additional interface (this is allowed and part of the software contract) that provides additional facilities. So that the interface isn't restricted by hard coding I have created configuration files that identify table field names, label descriptions, table column headers, table widths, column orders and properties used to create a tab control interface such as top,left,width (for the placement of text boxes) and group properties (used to create different tab pages). I've done this because I'm just a little concerned that if I leave the company they won't be able to change any of the intferface. I know I can't avoid hard coding validation but the data screens can be configured without hard coding. I currently use a tab deliminated file (so we can use commas in field names or sql commands) but will propbably change to xml as excel is rubbish for tab deliminated (places double quatation marks without asking) and I wan't a columned interface for users to read/write to the configuration files. What is everyone's thoughts on this. Time to retrieve and refresh data is important. The ability to travel half way around the world and create a 'dummy' sales order to enter into the database is also equally as important. Any advice would be gratefully appreciated. Fawxes An optimist's glass is half full. A pesimist's glass is half empty. An engineer goes and gets the right size glass.

    1 Reply Last reply
    0
    Reply
    • Reply as topic
    Log in to reply
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes


    • Login

    • Don't have an account? Register

    • Login or register to search.
    • First post
      Last post
    0
    • Categories
    • Recent
    • Tags
    • Popular
    • World
    • Users
    • Groups