Is KaioneSoft SprintDB dead?

[N2O2]

KaioneSoft SprintDB has not offered a solution for WM6. They still sell a patched version of their PPC2003 software that sorta works with WM5. At the KaioneSoft website there no signs of life since August 06 and I believe they are no longer active(except to collect money selling obsolete software).

My questions to the group:

Have you migrated out of KaioneSoft SprintDB?

If so what did you migrate to?

Thanks for your help,
N2O2

[mlk]

I am currently helping them with a WM6 version - as you would be aware, the major issue is the difference in the synch, otherwise SprintDB works well in WM6 - think we are reasonably close to a solution... dont worry, I was getting mightily frustrated myself with this lack of movement. I now have the ability to synch - albeit not quite as elegant as previously.

[N2O2]

Thanks for the response. And thanks for helping out SprintDB project.

Unfortunately a database solution without synchronization is not useful to us. For our application to function we need to share data...

My concern with SprintDB is that they move so very slow. So ok, thanks to you, we are near a solution for WM6. Where will be when WM7 hits? Lost again? The newer operating systems are addressing some windows mobile shortcomings like security. These type of improvements more then interest me a little.

I've tested all the latest versions of our software on WM6 and SprintDB is the only one that won't function for us.

It would be good if KaioneSoft would keep us updated through their website, instead of pretending that the issue doesn't exist. Forcing their long time users to wade around the internet forums for solutions. I can't understand why they don't make the issue known on their website, unless they expect to sell to WM6 customers. I'm sure they refund unsuspecting WM6 purchasers, but not being forthright about the issue is more then a little shifty. I'm questioning if this software vendor is responsible enough to trust my databases to.

I have stopped further development with SprintDB and we are testing other solutions. So far Syware is the leading candidate and appears to be a very active company. Has anyone other opinions on database software for WM6?

Long time SprintDB user losing confidence,
N2O2

[pmernyk@hotmail.com]

Hi, I've been using a SprintDB Pro database I developed a couple years ago, and now I'm looking at upgrading to a new device with WM 6. I use this app everyday, now have over 8000 records, and I was so bummed to learn that (1) ActiveSync 4.5 it seems does not support sync'ing databases anymore, and (2) SprintDB doesn't sync on WM 6. I would hate to have to ditch this thing and start over on another db product.

Any advice? Without the ability to sync on WM 6, then what? Can I at least back up my database? Would there be some other way to convert the cdb to something i can edit on the PC?

Any idea *when* SprintDB will fully suport WM 6? (Call me cynical, but hearing "I think we're reasonably close" does not sound to me like a release will happen very soon.)

Does anyone know more about this ActiveSync 4.5 limitation? Does that mean I just need to stay with an older version, or is there more to this?

Finally, if it does come to switching products, any other suggestions besides Syware (which I will check out)? Do any allow me to convert my forms, macros, etc. from SprintDB?

Thanks for any answers or advice!

[N2O2]

Wow, an impressive set of questions.

First off MLK (http://forum.xda-developers.com/member.php?u=252229) is correct the program itself functions properly under WM6, the issue is with the sync. The sync issue exists because M$ removed Mobile Access support starting with WM5/ActiveSync4. SprintDB developed a work around that made AS4 function with their program that was designed for PPC2003. That work around no longer functions WM6. because M$ further slashed AS4.5

WM6 requires at least AS4.5 or Vista.

SprintDB told me in March 07 that a WM6 sync fix would be available in July 07. We are still waiting. In SrintDB's defense: I think this task is substantial, they are attempting to develop an Activesync type database sync with a deliberate slash of support by M$ in AS4 and 4.5.

It sounds as if you don't need to merge your PC database(mdb) with your WM database(cdb). If you can get away with simply converting your cdb to mdb and back to cdb, although a bit clumsy a program like "Access Converter" free from Kaisoft may be a work around. You could then stay with SprintDB saving the development cost of a migration.
http://www.pocketkai.net/asp/en/index-en.html

If you need to manage two databases the merge their contents ie WM6 <-> W2K the only solution I see is ODBC. This has the advantage of syncing your data via cell or Wifi connection. Unfortunatly this will involve having to redevelop your forms queries structure in another DB program such as Syware. I'm not aware of conversion utilities to migrate from SprintDB to another aplication. (Hint to developers reading in: You could gain the entire customer base from SprintDB if you offer such a function.)

I'm still looking for other DB options if there are suggestions.

Hope this helps. Good Luck.

[pmernyk@hotmail.com]

Thank you N2O2, that was a very thoughtful reply and quite helpful.

The word I got from KaioneSoft Support is they expect to have a new version with sync for wm6 in about 1 month. If that happens, I'll be happy. Meanwhile, it sounds like Access Converter will let me squeak by until that release.

[ozo]

The word I got from KaioneSoft Support is they expect to have a new version with sync for wm6 in about 1 month.

KaioneSoft sends this answer every month, does this whenever you send a message that requests the solution to this problem.

[mlk]

Sorry guys, meant to correct this ages ago & only just noticed... new version is out & works with full sync - not as good as previous in that you have to initiate the sync, but at least it works.

Further to this, if the PPC has low memory, or the DB is "of a size" then sometimes the sync can incorrectly report a successful sync - I have another beta I am testing that looks to resolve this, so go 4 it, it looks like they have come through at last.