Data collection storage options

From: Wapiti (testme_at_spamcatcher.org)
Date: 08/06/04 

Date: Fri, 6 Aug 2004 14:53:54 -0700

Tough decision for me. I'm faced with the need for RAD - short timeline.
I'm replacing an existing handheld app I wrote several years ago for an
intermec device using vc1.5 with a newer one written for ppc devices (vb.net
cf).

My question pertains to what file types to use when storing and manipulating
the data on the pda. My old app stored data using random access text
files - but it was a bit combersome to develop. I do like sql.

The specific ppc devices are yet to be known, but I need to continue
development regardless. The app may need to be ported to other ppc devices
too (just a side not if its even important at this point).

I'm trying to figure out how I should best store and work with the data
files (inventory, issues, receipts, transfers) on the pda: Text files, sql
ce, other?

A parts file will be downloaded (in flat ascii text format) to be used on
the pda (user enters a part number, the system will look up the part and
display the uom and location) - and this file could be relatively large
(several thousand parts possible).

My old program retrieves this parts file, via zmodem comm transfer, and
immediately parses it into a random access text file (then discarding the
original server fed file). When the user enters data (inventory, issues,
etc), it is stored in its respective random access file (inv.dat,
issues.dat, etc). When the user wanted to upload their collection info,
the system would export the data to a flat file and send it, zmodem, to the
PC. To build the flat file, the system would read each .dat file in turn
and write a record to text file containing all transactions - preceded by a
record flag (I=Issues, N=iNventory, etc).

The legacy server system cares less how the pda will work with the data when
its out in the field, but it does require that it accept the parts.txt file
as is, and it requires that the file received from the pda (collect.txt) is
in the same spec'd format.

Is the 'sqlserver for ce' method the best way to go? Or are random text
files handled pretty well (easy to develope and quick to access) under
vb.net cf?

Any helpful input and or experiences shared would be appreciated,

Thanks,

Mike

Relevant Pages

  • Re: Data collection storage options
    ... Random access is pretty good with the .NET Compact Framework. ... Approach 2 -- Port data handling to Sql CE. ... you to do this after you have all the rest of the app done *and* what you ... > the data on the pda. ...
    (microsoft.public.dotnet.framework.compactframework)
  • Re: Announcement: Multivalue on a PDA
    ... on a regular QM server and then just dump the BASIC app on the PDA. ... purely for developers and really has nothing to do with end-users. ...
    (comp.databases.pick)
  • Re: Announcement: Multivalue on a PDA
    ... character app in Windows CE. ... PDA, do you really expect people are going to use a stylus/pen to ... Developers think that because of the limited real estate on a PDA they'll make things smaller. ... Don't just convert your desktop interface to a PDA. ...
    (comp.databases.pick)
  • Re: Detect Cradle
    ... If I go with "Notification on the Desktop PC when ActiveSync start ... synchronization" then I should be able to run an app from the desktop. ... This was in reference to doing data syncing between the PDA and the ... "executing pocket pc program from activesync" in this newsgroup. ...
    (microsoft.public.pocketpc.developer)
  • Re: Disabling the touch screen for Pocket PC
    ... > buttons has already been mapped and there is no need to tap an 'ok' on ... At the moment the app is working fully ... its been done on the keyboard of the pda. ... > See the ErrorOKPress is the bool that simulate the enter key on a ...
    (microsoft.public.dotnet.framework.compactframework)
Loading