Re: Pocket Access

From: CodeBubba (broeser_at_cfl.rr.com)
Date: 12/11/04


Date: Fri, 10 Dec 2004 22:48:39 -0500

David,

Gotcha.

One thing I did discover, though. While experimenting (before I had too
much data) I backed up the db across Active Sync to my main machine. The
forms were stored as tables as far as the PC version of Access was
concerned. I even upgraded the MDB to Access 2002, copied it back to the
PPC and everything was still intact; so exporting the forms separately might
not be necessary.

Also - I discovered a small bug in the program; loading queries from
shortcuts crashed the program. I sent a bug report to the author and less
than 12-hours later he sent me an updated EXE which fixed the problem. Wow
now *that's* service!

-bruce

"David C. Holley" <DavidCHolley@netscape.net> wrote in message
news:edxKbMl3EHA.2676@TK2MSFTNGP12.phx.gbl...
> Just be certain to periodically export your forms. If you delete the db
> from the PPC and/or replace that's the only way to save them. Also, I
> think that there's a bug with adding a certain number of records (20-45)
> via form at one time. I've had a couple of instances where the records
> that I've added have ended up not being saved. Overall, REALLY, REALLY
> good.
>
> David H
>
> Bruce Roeser wrote:
>> David,
>>
>> Good suggestion. I just checked out and purchased a copy of DBAnywhere.
>> Man ... is this ever a *great* program! Impressive!
>>
>> I've been looking for some programming capability for my PPC for some
>> time - I've looked at NSBasic and some other things but nothing quite
>> filled the bill. (I just didn't feel like re-inventing the wheel
>> anymore - I've done that enough times!) Then I realized that a DB
>> program was what I was looking for - this really hits the spot; and it's
>> cheap, too. I think it's been the flexibility of a database/forms engine
>> I've been needing all along.
>>
>> Thanks again!
>>
>> -bruce
>>
>> "David C. Holley" <DavidCHolley@netscape.net> wrote in message
>> news:%23Nra2wA3EHA.3236@TK2MSFTNGP15.phx.gbl...
>>
>>>Actually, Pocket Access isn't Pocket Access like Pocket Word is Pocket
>>>Word. Pocket Access only takes a Access db and compresses, compacts and
>>>condenses the db into a *.cdb file onto the pocketPC. Its up to you to
>>>utilize a third-party program to access the data. I personally use DB
>>>Anywhere available from www.pocketGear.com since it supports forms &
>>>programming.
>>>
>>>David H
>>>
>>>Todd Ogasawara, MVP Mobile Devices wrote:
>>>
>>>>See if the Microsoft Access section (and the links associated with it)
>>>>in my
>>>>Where Is It for the Pocket PC QuickFAQs at...
>>>>
>>>>http://ogasawalrus.com/mobileviews/mobilefaqs/WhereIsIt
>>>>
>>>>...answer your current and probably some followup questions.
>>>>
>>
>>



Relevant Pages

  • Re: Is this a bug?
    ... No it's not a bug. ... The design of the PPC ... >> So, this is not a bug, it is a user selectable option. ... >>>at the tp right hand of the screen the audio stream does not stop, ...
    (microsoft.public.pocketpc)
  • Re: how to remove registry keys on uninstall?
    ... The PocketTV Team wrote: ... You mention the bug you say in PPC 2003 SE where only registry values ... If at this point if I tap 'Yes', ...
    (microsoft.public.pocketpc.developer)
  • Re: VS2005 Beta2 vs VS2005 Release
    ... held at some other place i'm interested to discover other persons ideas ... The explanation of 'we found this bug earlier and are trying to decide ... In the case of finding a compiler-bug we're not talking about consumers ... In your case it's a detailed explanation of where the problem is, ...
    (microsoft.public.pocketpc.developer)
  • Debugging - catching runtime errors and a comment...
    ... euphoric rush you get when you finally find the bug worth the ... gnawing frustration of debugging needed to discover it? ... I remove all errorhandling code. ... The download of the specified resource has failed. ...
    (microsoft.public.access.formscoding)
  • Re: RfD: Legacy Word
    ... word in the command line, finds a bug, and wants to ... MARKER cannot help here ... When you discover mistakes, the offending code is simply removed. ...
    (comp.lang.forth)

Loading