I might be able to use ExecuteAssembly, but it's going to take a bit more work than I want. I'll try it out. BW

This would work fine too...only thing is I'd have to re-run wsdl if I added another method to the web service. It' really just a few more steps, but it would be nice to avoid them if I could. If I ever dig anything up on why it's not working as expected, I'll be sure to post the solution to this thread.

Yes, that's what I had read also and I'd figured other project types would do the same, so I was surprised at the runtime exception... I think maybe I'll try the .NET forum...this problem is hard to classify.

The type is showing up as decimal in the data designer. Strangely, it now seems to be working, without any real intervention on my part. The only thing I did, was to try changing the Bid type to Numeric (still didn't work) and then back to Decimal (now working). The only thing I can figure is that somehow it was wrong in the designer, but by going through my changes I managed to get it to change to the correct type...? This is in spite of the fact that I'm fairly certain that from the start I had the type as decimal in my table. I'll be designing some more tables, so I'll try to be sure to pay very close attention to what I'm doing, in case it happens again. BW

You can try one that I wrote: filebackup.sourceforge.net It is written in C# using .NET 2.0 and the source is available and it's FREE. I am sure it would not be considered the best, but it is very easy to use and it does scheduled backups (which have never failed in my tests). It uses the date change on a file as criteria for backup. As with all software I am sure it could use some improvements. A few limitations: 1. It doesn't remove directories from the backup destination area that are no longer present in the backup source area. 2. It doesn't do compression. 3. It doesn't do incremental backups. 4. If you select a subset of directories in a parent directory (i.e., not all child directories are selected) and then subsequently add a directory to the parent directory, FileBackup currently has no way of knowing that the new directory has been added and therefore will not back it up. A point to keep in mind: The fact that a person would select a sub-set of directories implies that they may not want a newly added directory to be backed up anyway. So, whether this should be automated or not comes into question. Just being aware of this point will ensure that you modify your backup profile as required. 5. It will not backup files that are "locked" by an application. As well, it will not backup things like the registry. This could be handled by taking advantage of the Volume Shadow Copy mechanism that Windows XP can make use of. If these limitations are not a worry to you or if you have some coding skills in C# you can make it do whatever you would like it to do. modified on Monday, February 18, 2008 1:50 PM

Well, no replies so far...maybe a different question... Does anyone know where to find a *thorough* tutorial/article on using a .config file for remoting? And please don't say "just do a search, there are plenty out there," because every one I've seen so far is most certainly NOT thorough. Even the articles I've found on MSDN generally only touch on a few of the possible configuration features. The doc on the schema of configuring for remoting is also noticeably out of date. If someone could point me to one they already know of, though, that would be very much appreciated. That said, if I don't get an answer here or elsewhere...I've got Rammer's book on the way, so hopefully I'll find what I need in there (but an earlier answer would be nice :) ). Thanks for any help. BW

Thanks. That seems to be pretty much what I ended up doing. The article I was going off of called it an event shim. One thing that isn't really clear to me is why the wrapper/shim works. In other words, you can't just do service.OnLogData += handler_formyevent; You have to give it to the wrapper, which can subscribe (why, I'm not entirely sure), and then subscribe to the events that it raises. MyEventWrapper w = new MyEventWrapper(); service.OnLogData += w.WrapperMessagehandler; w.OnWrapperMessage += handler_formyevent; hmmm...is it because the wrapper is known to both assemblies that it works, whereas doing it the other way, the service isn't really aware of the subscriber? So in the scenario where it doesn't really know about the subscriber it can't grab a remote reference to it, so that it can marshal the events over? I hope that makes sense...is it correct? BW

Well, coming from C# world...I expected it one place, and evidently my brain decided to see it only if it was in that one place. :laugh: Thanks again.

I believe that's it! I had an extra comma in there, and I think that's what was throwing it. Now I've got other problems to deal with :) Thanks for the help. BW

You might consider sending a note to Rich Grutzmacher, the Program Manager on the Office User Experience team. He helped coordinate one of the long-term, real-world studies conducted on early Office 2007 builds. Also see here. "Normal is getting dressed in clothes that you buy for work and driving through traffic in a car that you are still paying for, in order to get to the job you need to pay for the clothes and the car and the house you leave vacant all day so you can afford to live in it." - Ellen Goodman "To have a respect for ourselves guides our morals; to have deference for others governs our manners." - Laurence Sterne