Right away I would guess to say the information got corrupted and is usually due to devices being operated under low battery conditions. For me, low means below 50%. This is really critical when you are specially dealing with a bar code scanner which is not a standard item on a Windows Mobile device. Bar code scanner is an added drain on the batteries. I would check the typical usage of the device first and insure that these devices are recharged every chance they get and not made to go below 50% power whenever possible.
The Symbol devices are certainly more rugged as far as drops and physical abuse goes but as far as stability under low battery conditions is concerned I find them also unstable during low battery conditions. Corrupt databases and corrupt folder is something I have experienced in the past. I used to beta test Symbol products and bar code scanning was something I did using NSBasic also. I do not feel it is an NSBasic specific issue. Hopefully it is something you can resolve very quickly and get back to normal operations. Good luck Bob From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Chris Kenworthy Sent: Tuesday, September 30, 2008 2:21 PM To: [EMAIL PROTECTED] Subject: [nsbasic-ce] progra~1 on windows mobile device? Hi, I don't know if this is an NSBasic problem specifically, I doubt it, but there's a connection and I wondered if somebody here might have heard of this. A client warehouse using a barcode scanning program I wrote reported that my NSBasic program had disappeared from the device, and in the course of investigating, I found out that not only had the .nsb file and the sqlite .db file disappeared from the '/my documents' folder, but program files had somehow gotten renamed as 'progra~1', and so the built-in .nsb mapping to '/program files/nsbasic/basic.exe' or whatever wasn't working. We managed to restore recycle bin copies of the program and the database file, (missing some important barcodes that had been scanned,) and to change the name of program files back, but it seemed like a very weird symptom to get. The client is contacting symbol-motorola support to see what they make of something like that happening on their device, but is there anything else worth checking? As far as I can tell, the users weren't doing anything unusual with the device right before it happened. We've had some previous issues with file storage on the unit. Could the flash memory be faulty, or the file access ROM corrupted? Thanks in advance for any help. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "nsb-ce" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/nsb-ce?hl=en -~----------~----~----~----~------~----~------~--~---
