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
  1. Home
  2. General Programming
  3. Visual Basic
  4. App data storage on PocketPC

App data storage on PocketPC

Scheduled Pinned Locked Moved Visual Basic
discussionxmlperformance
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.
  • L Offline
    L Offline
    Lost User
    wrote on last edited by
    #1

    Hello, I am trying to determine the best option for storing locally-created data for a PocketPC financial analysis application. I have skimmed several books on PocketPC development, and searched the web and various newsgroups for opinions and guidelines on using flat files, binary files, ADOCE, SQLCE, XML, and other options **for local application data storage**; but have found little to crystalize my thinking/decision-making. The application is currently implemented using the basic FileSystem/File control with simple sequential operations. However, as I extend functionality, the data storage requirement expands accordingly - resulting in degrading app performance. So, I thought I would appeal to the PocketPC developer community for some assistance. I appreciate any thoughts on the subject. OK, here are some app details: 1) Financial analysis application where the user currently enters 60 - 200 inputs that need to be stored on the PocketPC 2) The data can be grouped into 5 generic categories, each containing 12 - 40 data entries 3) Need to support exporting of user entered data, and approximately 320 app-generated result calculations (for importing into Excel /MS Office apps on desktop PC) -- a total of 380-520 data items per exported file. 4) Snappy performance when loading and saving data files is desirable 5) The solution can employ either multiple files for each analysis (e.g., user data file + app results file + app export file that combines user data and app results) or a single file containing user data and app results Thanks in advance, Donovan Dillon.

    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