SharePoint - Office 2003 limitations in MOSS 2007 Document Libraries

If Office 2003 we have noticed the following oddities using Document
Libraries. Is it a requirement to use Office 2007 to avoid the issues below?

Requiring check out does not work right. The user is not given the
choice to open read only or check out. The file opens as ready only and then
when you try to save it you get an error that the web server is busy. It
works properly when Word 2007 is installed on the client PC.
When requiring check out is turned off a user is still not given a
choice to open read only or edit.  The document opens as read only but can
still be saved to the library. When using Office 2007 everything works
correctly.

  Daniel Webster replied...

That sounds about right for the current behaviour.
Office 2003 will still overwrite a checked out document in Save As mode.
More fun stuff when mixing versions. . .
When storing native Office 2007 documents in a SharePoint 2003 document
library, downloads even to a client with Office 2007 installed are
downloaded as zip files.The extensions then need to be changed back to the
docx or pptx extension.

SharePoint MOSS 2007 fails during full installation even id 27745 We have SQL 2008 installed on but in same domain, installed all as per the instructions here http: / / blogs.msdn.com / sharepoint / using full installation. Started wizard, inserted sql server \ instance name, username / password, port number. It and long one having Admin_content. Did I miss something making fresh installation? I've installed sharepoint 2007 before on other 2 machines (one for MOSSportal and second with SQL2008 with instance everything went fine but now. . . . Errors in EvenViewer: 1) Event Type: Error Event Source: Windows SharePoint Services 3 Event Category: General Event ID: 27745 Description: The description for Event ID ( 27745 ) in Source ( Windows SharePoint Services 3 ) cannot be found. The local computer may not have the necessary registry information make sure that the database server is running. . - -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 2) Event Type: Error Event Source: Windows SharePoint Services 3 Event Category: Topology Event ID: 6141 Description: The site / could not be created Center at http: / / go.microsoft.com / fwlink / events.asp. - -- -- -- -- -- -- -- -- -- -- -- -- - 3) Event Type: Error Event Source: SharePoint Products and Technologies Configuration Wizard Event Category: None Event ID: 104 Computer: SERVER Description: Failed to create the configuration database. An exception of type Microsoft.SharePoint.SPException was thrown. Additional exception information: Unable to connect to database. Check database connection information

SharePoint update error 1, how can i do? [SPManager] [DEBUG] [2007-10-11 20:02:46 current status is Online. [SPDelegateManager] [DEBUG] [2007-10-11 20:02:46]: Begin registering Microsoft.SharePoint, Version = 12.0.0.0, Culture = neutral, PublicKeyToken = 71e9bce111e9429c. [SPDelegateManager] [DEBUG] [2007-10-11 20:02:46]: Using assembly manifest Microsoft.SharePoint.UpgradeAssemblyManifest. [SPDelegateManager] [DEBUG] [2007-10-11 20:02:46]: Registering [Microsoft SharePoint.Upgrade.SPConfigurationDatabaseSequence] for [Microsoft.SharePoint.Administration.SPConfigurationDatabase], Phase: 0, Order: 0. [SPDelegateManager] [DEBUG] [2007-10-11 20:02:46]: Registering [Microsoft.SharePoint.Upgrade.SPConfigurationDatabaseSequence2] for [Microsoft.SharePoint.Administration.SPConfigurationDatabase], Phase: 1, Order: 0. [SPDelegateManager] [DEBUG] [2007-10-11 20:02:46]: Registering [Microsoft.SharePoint.Upgrade.SPContentDatabaseSequence] for [Microsoft.SharePoint.Administration.SPContentDatabase], Phase: 2147483647, Order: 0. [SPDelegateManager] [DEBUG] [2007-10

SharePoint WSS FAQ additions and changes - 11th - 17th June 2007 Note: All of the addresses of scid = kb;en-us;939015 Support WebCast: Microsoft Office Outlook 2007 integration with Microsoft Windows SharePoint Services (WSS) version 3 Contact Lists and Document Libraries 15th June 2007 http: / / support.microsoft.com / default.aspx?scid = kb;en-us;937208 Description of the SharePoint Server 2007 hotfix package: May 15, 2007 14th June 2007 http: / / support.microsoft.com / default aspx?scid = kb;en-us;937203 Description of the Windows SharePoint Services 3.0 hotfix package: May 15, 2007 14th June 2007 http: / / support.microsoft.com in the search results when you use an SQL query to sort search results in SharePoint Server 2007 14th June 2007 http: / / support.microsoft.com / default.aspx?scid = kb;en-us;937904 Description of the SharePoint Server 2007 hotfix package: May 25, 2007 (2nd one from May 25) 13th June 2007 http: / / support.microsoft.com / default.aspx?scid = kb;en-us;937949 You cannot upgrade SharePoint Portal Server 2003 to SharePoint Server 2007, and you receive an error message when you run the Prescan.exe tool

SharePoint sharepoint db issue This is a multi-part message in MIME format. - -- -- - = _NextPart_000_000D_01C8068E.C4C29BB0 Content-Type Transfer-Encoding: quoted-printable Let me just start by saying I have no clue about sharepoint so I'm = learning as I go. So here is the issue that was just handed to me. On our web server that = is running sharepoint, I'm getting errors in the EventViewer stating it = cannot connect to a sharepoint database on the database server. I get = this error once every hour during the day my question is, how can I = find out what is trying to connect to this sharepoint database? Its a = sharepoint site, but how can I find out which one? = 20 SharePoint is the only thing running on the web servers were the error = is happening. - -- -- - = _NextPart_000_000D_01C8068E

SharePoint Using Sharepoint 2010 for data storage but still running full Access client with vba and normal forms Kallah wrote that with Access 2010 it was possible to store access 2010 data on Sharepoint 2010 but still run the Access client in windows much as a "normal" access client, accessing the data on Sharepoint 2010. sits on SharePoint. You can also have the application sit on SharePoint and a copy gets pulled down sure local machine when you click on and on the SharePoint site, you will need access installed for this to occur. So, in this case we even replication via the internet. This seems much slicker. Again my interest is data on sharepoint 2010 and use normal windows / Access clients on each user's PC. I am not