Carl,

I understand what you are saying about the end users.

I only raise the issue because changing the computer name may break a lot of other things about their network.

I believe it's better for the app to work with the network, than requiring the network be configured to the app.

>"If it's because of some code you've written you need to rethink the design to make your code work with the way the user has configured their machine."
>Erm no.... This APP isn't evan finished yet. The reason why I need to have the option of changing our customers computer names is because the companies core software (written in Sculpture) prints to till printers often set up on windows machines, it has shop floor / back office & warehouse logins which will print to a set path (computer name) & a printer name, because our customers are non-computer literate (I mean that in a nice way) we often get allot of support calls where either they have re-installed windows or in a couple of the examples some of the weekenders have messed with the computer settings (I dont know why they do it either ?) So instead of talking the customers through each an individual settings (right click on my computer or type in IPCONFIG etc) its easier if I have all the settings in one application. So no its nothing todo with "some code i'd written" or needing to "rethink my design"....