Deploying XML for a single user database

Old Bob

unread,

Jul 1, 2009, 11:12:39 PM7/1/09

to

I recently upgraded an old Paradox-based database application, and
decided that the new version should use an XML database for reasons
of speed and reliability (among others), and the conversion and
update went smoothly except for 1 thing: Although everything works
as designed on my system, when deployed on another computer it
throws an exception and dies. I'm not sure where the exception is
because the address given appears to be in the DevExpress grid
component, but I've never had a problem with their components
before. Anyway, since I'm new to the XML world, I'm guessing that my
lack of knowledge is my problem. Are there any files that I need to
add to the installation file, other than the main executable and the
BDE (to handle the Paradox to XML conversion), or should I switch
back to Paradox? Any advice or tips are appreciated.

Bob

--
--------------------------------- --- -- -
Posted with NewsLeecher v3.9 Final
Web @ http://www.newsleecher.com/?usenet
------------------- ----- ---- -- -

David Kerber

unread,

Jul 2, 2009, 7:50:00 AM7/2/09

to

In article <4a4c25a7$0$26104$586...@news.usenetserver.com>, o...@cave.com
says...

> I recently upgraded an old Paradox-based database application, and
> decided that the new version should use an XML database for reasons
> of speed and reliability (among others), and the conversion and
> update went smoothly except for 1 thing: Although everything works
> as designed on my system, when deployed on another computer it
> throws an exception and dies. I'm not sure where the exception is
> because the address given appears to be in the DevExpress grid
> component, but I've never had a problem with their components
> before. Anyway, since I'm new to the XML world, I'm guessing that my
> lack of knowledge is my problem. Are there any files that I need to
> add to the installation file, other than the main executable and the
> BDE (to handle the Paradox to XML conversion), or should I switch
> back to Paradox? Any advice or tips are appreciated.

I don't know about the conversion issue, but the words "speed" and
"XML" are mutually exclusive. We tried xml for one of our applications,
and it saturated the cpu and bandwidth at 1/10 of the required load.
It's just too "wordy" (too many characters transmitted for the amount of
actual data), and takes too much cpu to parse the data out of the xml
tag structure.

--
/~\ The ASCII
\ / Ribbon Campaign
X Against HTML
/ \ Email!

Remove the ns_ from if replying by e-mail (but keep posts in the
newsgroups if possible).

Old Bob

unread,

Jul 2, 2009, 7:29:24 PM7/2/09

to

Thanks for the advice David, I've always used Paradox for my database applications, but after
reading countless reports of Bde problems and corruption issues with Paradox files, I thought
this was the time to make the switch. Since this application is designed for a single user, I'll
probably dump my xml experiment and go back good old Paradox :)

Bob

David Kerber

unread,

Jul 6, 2009, 7:57:30 AM7/6/09

to

In article <4a4d42d3$0$5339$386...@news.usenetserver.com>, o...@cave.com
says...

> Thanks for the advice David, I've always used Paradox for my database applications, but after
> reading countless reports of Bde problems and corruption issues with Paradox files, I thought
> this was the time to make the switch. Since this application is designed for a single user, I'll
> probably dump my xml experiment and go back good old Paradox :)

There may be other options besides Pardox for dropping the BDE (mySQL?),
but I wouldn't list XML as one of them unless your performance
requirements are quite modest.

D

....

Marcel

unread,

Sep 3, 2010, 3:02:58 PM9/3/10

to

If the path to your XML in the connect object is set at design time, make sure you're connection
object is not connected while compiling....

'Marcel