Louis Kessler’s Behold Blog     The Behold User Forum

... at the "asInvoker" level. I researched into how to set up the manifest file (it's XML) and then how to embed it as a resource in Behold as required. So the problem must have been the request of an elevated run level, but it doesn't say what part of the program was requesting the elevated run level. 3. "Application did not pass multiuser session compliance check". ...

... in my view, and as I said a month ago, think it needs to be brought up-to-date (via XML and Unicode), and maybe could use a few improvements. I'm talking about tweaking - not a major overhaul, An evolution and not a rewrite. But I think I found out what's going on and why the opinion is that GEDCOM is bad. Over at the BetterGEDCOM blog, a blog site run by some of the ...

... does a decent job. I think GEDCOM only needs a few tweaks: maybe convert it to XML and make it Unicode. Add Places and Citations at the record level. And update its handling of media files. But there are some people that think that it needs more. A new site has been created called BetterGEDCOM and its at bettergedcom.wikispaces.com. This is where a number of ...

The work continues on splitting Behold's Everything Report into pieces. But while I do spend a lot of time working on Behold, I also spend time keeping up to date on what else is happening out there with regards to genealogy software. Most of you know I've set up GenSoftReviews, which now pretty much runs ...

Now where will this path lead me? Two posts ago, I thought to convert to using XML as my internal data structure, since it's equivalent to GEDCOM and I had an XML library available. The library wasn't bad, but when I looked closer at it, I saw it was effectively using a simple tree structure. So then I thought to load the GEDCOM ...

... for handling the internal data. But I may have discovered something even better. XML (Extensible Markup Language) is a new technology developed to transport and store data. It contains start <TAGS> that are closed by ending </TAGS>. Between the start and end tags is the value associated with the tag. Tags can be nested. Hmmm. GEDCOM looks like this: 0 ...

This blog title could very well have started an article about genealogy research, but in this case I'm talking about a quick websearch I did to find a fast database package for Behold. In yesterday's blog post, I mentioned Accuracer by AidAim. They had posted how fast their database was and even gave ...

... is that it inputs GEDCOM and outputs GEDCOM, but stores everything internally as XML, which is the new web standard for storing data that Microsoft has embraced. Several attempts have been made to come up with a GEDCOM XML, but this one is straightforward and uses new XML handling functions from ...

... Some of his ideas are very innovative, e.g.: Report Generator, Spreadsheet output, XML output, making Places an object, Unicode, and (the one I like the best) allowing entry of Pets. Of course, his GenoMaps is the main innovation upon which the program is based. Reading through his material is quite worthwhile. What is ironic is that despite my really relating to ...

... something that would be outdated very quickly. Object definition languages (such as XML) are likely to contribute to meeting these needs." But Family Tree Maker continued to use it, by putting the underscore before it which indicates a custom tag, allowed by GEDCOM. Until I found this out, I was going to put in full SCHEMA support into Behold. That would have entailed ...