IT & Infrastructure

How did I miss that? No, don't answer that! Thanks Chris. Rodney

Good Grief, The millions of things that could be going on there boggles the mind, to start I would check the directory where the program has been installed. See if there is a .log or .err or .txt file in there, it may be a log file that could provide clues as to whats going on. Regards Ray "Je Suis Mort De Rire"

Try the the Unicode home page: http://www.unicode.org/ Check under the "Useful Resources" link. Hope this helps. WillCodeForMoney

I would say you need to look into using XML for this project. You can insert and retrieve nodes any place within the document without the temp file/copy/write procedure.

Thanks for tip! Got it functioning the way I would like. Hmmm.. that seemed all to easy. I'll have to think of a harder one next time. ;P "Why are we hiding from the police, Daddy?" "We use VI, son. They use Emacs."

MFC works perfectly under Windows CE, but I have always avoided it. If you use the Win32 API directly you get better performance, and, often, uses lesser memory. Some things are a lot more easy/faster to program using MFC, but what you use totally depends on your application, and the devices it's going to run on. - Anders Money talks, but all mine ever says is "Goodbye!"

Well, I was trying to dig up the batch file for you, so I could send it your way, but our IS group has once again moved stuff about and I don't see it anymore (probably on a secure server). :(( So ... you should be able to check the dos error level coming back from Analyze (i.e. if errorlevel = 1 goto BadData ) to determine if a problem occurred. Also, if you look in the VSS on-help, you'll find examples on how to handle using the Ananlyze Utilitiy, the command-line prompt, and those switches that need to be set in order to properly handle problems. It provides for an active dump to a text file of issues found and resolved (we run ours every day). Now, if your database is so trashed that it's dumping Analyze out with no chance to fix the problems, then you have much deeper issues at hand. Does that help any? :confused: Hope so. D.

You could try ShGetPathFromIDList( );

No there are no rules for what should be an attribute and what should be an element. It's just up to you to decide what would work better for you application. Generally though an attribute should be one or two words, anything more should be an element. Another thing to consider is how you may need to use document. If for example you have a name element with child elements for first name and last name you could obtain the nodes by first or last name, or just the name nodes. You could do the same thing with attrbutes but not as cleanly in my opinion.

It may seem obvious, but you need to use a install program such as Installshield or Wise.