Some for you: if you have a problem then explain it clearly. If you are asked for more information, provide it. As tyou do not pay for the help here, don't expect other people to do your work for you. And finally, learn some manners.
One of these days I'm going to think of a really clever signature.
I would guess you did, but you didn't say so in the question. Taking a rational approach, we look to identify the first possible point of failure, and work up from there. Debugging would probably be more beneficial then experimenting with different settings and platforms.
If you're convinced that the code is correct, I'd guess that the speech-engine does not have a "1" in it's dictionary, and being a non-existent word, it'd take the next best thing.
I'd guess that the speech-engine does not have a "1" in it's dictionary, and being a non-existent word, it'd take the next best thing.
Actually, that looks to be exactly the problem. The grammarbuilder only has two words loaded into it, "Black" and "White". Given that "White" and "One" both start the same phonetically, it seems quite likely it's getting a high match probability.
I am not sure I will word this correctly as it is currently outside my domain - but I would like some feedback on technologies to look at.
My main app is a GUI and a database engine - once a week data is taken from a large marketing database (58 million records, 400 variables, 39,000 discreet variable values) and compressed and highly indexed into my own proprietary database system - this enables the sales teams to run complex counts and analyses on standard laptops in sub second times.
Currently every monday the sales staff copy the database files to their local laptops (there is no actual data held so no names and addresses etc just bits and offsets)
However the database is now over 6GB and can take 10 minutes to copy on the local network and ages (technical sales term) for those working from home. So I want to write a system where the database is held centrally with a server of some description which my app can talk to specify the information required and receive the results. It could foreseeably have up to 100 users at any one time.
So... my question... what technologies do I need to be looking at? Will WCF suffice?
Last Visit: 31-Dec-99 18:00 Last Update: 19-Dec-13 17:06