|
|
|
|
|
|
|
|
Frequently asked questions regarding Data On The Run:
I am unable to set up synchronization with ActiveSync 4 ActiveSync 4.5 is not supported; version 4.2 or earlier is what you will need to use with Data On The Run. If you have installed version 4.5 of ActiveSync and you wish to use Data On The Run 4, you should remove ActiveSync 4.5, install version 4.2, and then Follow these instructions..... (you will need to repeat installation of Data On The Run after reinstalling ActiveSync 4.2).
What is the "Compact Framework?" Do I need to update my device? The compact framework page provides a list of devices and the version of the compact framework they shipped with. More information is also available at the user guide.
I'm seeing a "Cannot find Data On The Run" (or one of its components) error. Your device needs the compact framework to run Data On The Run. See the compact framework page for more information and a download link.
How do I transfer an Access database to the Pocket PC?
Is the unregistered download version feature limited?
How do I register Data On The Run?
I bought the full version, and it is still saying the program is expired!
I'm getting error messages when I synchronize with the desktop.
How do I upgrade to the latest version?
My data is not synchronizing with the desktop.
Do I need any other software for Data On The Run? What is "Pocket Access?"
Windows Mobile 5 devices will give this error whenever the software is uninstalled, or if you reinstall over an existing copy of Data On The Run. It can be ignored. Should you experience problems you can also clear the error by temporarily changing your regional settings to US English on the Pocket PC, repeat the installation, verify everything is working OK, and then you should be able to change your regional settings back and everything should still work OK.
Most error messages can be fixed by doing one of the following. First, if your regional settings are not set to US English on the Pocket PC, try setting the regional settings to US English and reinstalling Data On The Run. You can later change the regional settings back. Next, if you are getting errors while running Data On The Run, another program may have replaced or un-registered some of your system files. Try reinstalling Data On The Run and answering "yes" when asked if you want to replace the existing files (Bluetooth manager users on the iPAQ should say no if asked to replace any files beginning with "ado").
Special thanks to Jim for helping troubleshoot this problem!
ActiveSync can give errors if you have a date field and there is a date in it that is either too far in the past, too far in the future, or not a valid date. Try sorting your table by the date, and look for dates that are possibly causing a problem. You can either change these dates to a more recent date, or change the field type to a text field. We are not exactly sure what the range of valid dates is, but if you have dates back in the 1800's listed, you are probably going to have some problems synchronizing.
When I transfer my database, I see the message "This function is only valid in Win32 mode". Check the dates in the date fields in your tables. ActiveSync has trouble with dates that are really far in the past, or really far in the future. Check to see if you have a date that is, let's say, in the 1800's. We are not sure exactly how far in the future or in the past the date has to be to cause this error.
I don't see the queries and forms from my desktop computer in Data On The Run. The "Pocket Access" file format, which Data On The Run uses, does not contain the queries, forms, reports, or macros from the desktop. You can, however, recreate queries within Data On The Run using the query builder, and use the built in Form and List view tabs to view and work with the data on your device.
I can't install, I get a message that says "CEAppManager not found, reinstall ActiveSync. Try visiting the downloads page and using one of the "over the air" installation packages - just copy the over the air installer to your device, and tap on it with File Explorer to install.
I can't go to Form View or List View, or I am getting other error messages Check your database file for characters such as ? or * or & or other symbols like that. If you have these symbols in your field names or as your table name then you will likely experience problems.
Windows Mobile 5 users should disconnect their device, launch Data On The Run on the device, then do a soft reset and reconnect and try again. Also, sometimes rebooting the desktop computer will fix this. In addition, if you are transferring to a storage card, try using the path as "Storage Card\My Documents\mydatabase.cdb" instead of "\Storage Card\My Documents\mydatabase.cdb" - omit the first \. Another user reports: "Thanks for that; the reason access was denied is because I already had synchronization set up between my Access data and my other Pocket PC running PPC 2003. I was transferring files to this device and then syncing. I have found that I had to delete the relationship on that device and then manually delete the .cdb files on the new device before active sync would allow me to set up a new arrangement." Also, one user has reported fixing this error by reinstalling the Microsoft Data Access Component file MDAC.exe. If you are unable to resolve this, please contact us.
This is probably from adding a new record or modifying an existing record on the device, and leaving a required field blank on the device. If this field is marked as required on the desktop, but it is blank in Data On The Run, ActiveSync doesn't sync the changes. You can either make sure you do not leave any fields blank on the device, or you can go into design view in desktop Access and make sure that the fields are not marked as "required" and "Allow Zero Length String" is set to yes.
This is an ActiveSync error and we are not completely sure why it happens. One user reports "All I did to fix the error is soft reset my device and it synced just fine" Here is some information from another fellow user who experienced this problem: "I clicked on "Options" and "Pocket Access" in ActiveSync, removed all the database sync settings listed there, then deleted my partnership and reestablished it with a new name, and set up synchronization again. I also noticed that the problem began after receiving a database as a file attachment in my Inbox. I moved that e-mail to a folder that did not sync with the Pocket PC. Then I set up database synchronization again as described in the transfer page. I am not sure which of these steps did the trick but I can now synchronize without the error."
ActiveSync says "Error Converting File, Conversion Failed, The specified module could not be found. Two users have reported that removing and reinstalling ActiveSync has fixed the problems. If you have this error and try reinstalling ActiveSync, let us know if it fixed your problem.
I'm receiving an "Invalid Property Value" error message with Data On The Run. This issue is now resolved; download the latest version.
There was a database format change with Windows Mobile 2003, so to run earlier versions you will need to use Microsoft's database conversion utility after installing. See this page for more information and to download the utility: Microsoft Database Conversion Utility
One user reports "I found an unexplained copy of the database file on my hard drive. As soon a I deleted this copy the Pocket PC synchronized without any problems." Another thing that frequently fixes this problem is to rename the database file to a different name, and then repeat the transfer process.
One of our users reports that if you are using "User Level Security" for your database you may experience problems if you are joining a workgroup other than the standard "system.mdw". Joining the system.mdw file and creating a new database, copying the tables and forms into the new database, and moving that to the device fixed this for the user.
There was a database format change with Windows Mobile 2003, so to run earlier files you will need to use Microsoft's database conversion utility. See this page for more information and to download the utility: Microsoft Database Conversion Utility
Thanks to Masters for his extra help in solving this problem. He reports "The combination of the device name, database name, and the user account name on the desktop computer can't be over a certain length". So, here are some ideas to try. Try shortening the name of your database file; something like "a.mdb" on the desktop, and then try the transfer. After that you can either try setting up a different user account (i.e. if you are a Windows XP user you'd set up another user account) with a shorter name, and you could also consider changing the Pocket PC device name to a shorter name (Start - Settings - System tab - About - Device ID on the Pocket PC).
I receive an error "Too few parameters. Expected 1" from ActiveSync. Check your table and field names for any symbols such as ? or * or & or ", etc. Symbols as part of table or field names can cause problems.
I receive a "Not enough storage memory" error during synchronization. Try a soft reset of the device, to free up memory and to make sure the file you are trying to synchronize is not in use. Then reconnect your device and try again.
How much memory is required by Data On The Run? Data On The Run 4 installation requires 0.75 MB of main memory, or 0.39 MB of main memory if installed to a storage card (this was on a Pocket PC 2002 device; your numbers may vary somewhat depending on the device).
How much memory is required by the .NET Compact Framework? The .NET Compact Framework is in ROM of newly released devices; to find out if you need to update the .NET Compact Framework, see this page. On a Pocket PC 2002 device, which shipped without any version of the .NET Compact Framework, installation required 1.58 MB.
I get "Error in ConfigDSN, ConfigDriver, or ConfigTranslator" when I try to set up synchronization. One user reports that disabling Norton Internet Security before attempting the transfer fixed the problem.
I'm getting an "Invalid character value for cast specification" error from ActiveSync. One user reports he changed the field type in his table from currency to integer: "I've changed in Access the type of field from currency to integer and I left formatting the same. It synchronizes perfectly"
I get a message about a "Sharing Violation" when I try to synchronize. Try closing any running programs on your Pocket PC before synchronizing. You can use a task switcher program or go to Start - Settings - Memory and close all programs.
How do I search for null/empty fields in my table? Use the "Advanced" "Enter SQL Command" feature from the menu in Query view. The syntax is "SELECT * FROM [MyTable] WHERE [MyField] IS NULL" (leave out the quotes, and replace the "MyTable" and "MyField" with your table and field names.
When I try to delete a file, it says the file may be in use and I can't delete it. Your database files will be in use whenever the device is connected to the desktop (in use by ActiveSync, because of synchronization) and also they may be in use if Data On The Run is running on the device. You can close Data On The Run by ctrl-q on the pop up keyboard, and delete the files using File Explorer on the Pocket PC when the device isn't connected to the PC. And if all else fails you can free up the in use files by doing a soft reset.
ActiveSync says "Data source name not found and no default driver specified" when I try to sync. Here is what one user reports: "I thought to go to the ODBC applet under "Admin Tools" on the control panel. No data sources were installed. Worse yet, when I went in to add MS Access as a data source, there were no drivers available to install. So, reinstall Access? Yeah, but that didn't help. turns out that "Data Access Objects" get installed with the operating system. On XP they should have been reinstalled with Service pack 2. But they weren't. Why they got deleted I don't know, but the only way I found to get them back was to reinstall Windows XP. Two hours later and KERBANG!! We've got database portability to the PDA."
I am receiving a "GregorianCalendarHelper" error. Try changing your regional settings to US English, doing a soft reset, then reinstalling the program. This worked for at least one user with this problem.
Your software doesn't quite do what I want. Can you recommend another program? We try to make the software as best we can, but realize that no software can do all things for all people. However, it is a policy not to recommend competing programs. It would be kind of like going to Burger King, telling them you really didn't like their hamburgers that well, and then asking them which McDonald's sandwich they thought was the best :-).
One user reports he fixed this as described here: The steps below finally returned the Axim to a working state. 1. rerun DOTR setup from \program files\data on the run installer. after next sync the checkbox for Pocket Access is back. 2. removed database syncronization settings from AS and removed cdb file from Axim. 3. copied mdb back to my documents on the Axim. I had noticed in the past that a sync would start almost as soon as I started the copy. The conversion window( the one with the tables to sync) comes up and I let it sit until the sync noted above was finished. At this point I would OK the tables to sync popup. |
|
The programs listed on this web site are trademarks of
Biomobility, LLC. All other products mentioned are registered trademarks or
trademarks of their respective companies.
|
