Many thanks for your response on this and I'm very sorry not to have acknowledged sooner. I've more or less decided to give up on this approach and await the release of 6.9.3. I only started looking at in any case after John Van Breda suggested that using SQL Server authentication with NBNUser would be the way to getting networking to work without Windows domains. I think this is not the case, simply due to the fact that, although you copy over NBNUser on NBNData when transferring the database from MSDE to SQL Server 2005, you will have no corresponding NBNUser login at the server level. And it seems impossible to create the server login retrospectively as it were, and get it matched to NBNUser on the database. (If anyone DOES know how to do the latter I'd be interested to hear from them).

I'm still not convinced any of this will work on a Windows peer-to-peer network as opposed to a domain-based network.

Cheers

Alan

John. Yes, I'm fully aware by now (see my first posting in this thread) of the concepts of server level and database level authentication. What I was not clear on was how to reinstitute the former and connect this to the latter following a migration from MSDE to SQL Server. The Installation Guide (Network editio p.9) does not explain this at all well. First of all nowhere does it state that you have to manually create a server level NBNUser login on the SQL Server (this might seem perfectly obvious from your end, but not to someone coming at it for the first time). Secondly, although it tells you to run the script, it does not adequately explain what this script is supposed to do.
Anyway, it looks a lot clearer now. I'll give it a go. Thanks.

Alan

Although not fully tested in this setup, I've seen Recorder 6 working successfully on Citrix simply by installing a workstation onto the Citrix box and making it available to the appropriate logins. Maps worked fine. It seems likely that you have a permissions problem with access to the C:\program files\Recorder 6 Worksation\Map Files folder (which you need full read/write privilieges on). You could test this by trying to save a notepad file in the folder, for example.

When you install Microsoft Office SharePoint Portal Server 2003 on a single server by using the default (Typical) installation options, you have an installation that uses Microsoft SQL Server 2000 Desktop Engine (MSDE) for your databases. This is fine in a small-scale environment, when you are hosting just a few Web sites. If your server gets more traffic or you need to start hosting hundreds of sites, you might run into performance and storage problems. If you find yourself in this situation and need to move to a more robust solution, you can switch to using Microsoft SQL Server 2000 Service Pack 3 (SP3) or later as your database. There are two methods you can use to switch your databases to SQL Server 2000:

Upgrade the databases to SQL Server on the same computer.
Use this option if you want to continue running SharePoint Portal Server on a single server.
Migrate the content databases to a server farm running SQL Server and SharePoint Portal Server.
Use this option if you want to move your sites to a server farm, with at least one front-end Web server and at least one back-end database server.

Roofing Vancouver