<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=Windows-1252">
<META NAME="Generator" CONTENT="MS Exchange Server version 6.0.6603.0">
<TITLE>save file</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->
<P><FONT SIZE=2>Hi all,<BR>
<BR>
Here is a strange problem I stumbled upon.<BR>
In my app I use a safe save procedure to save datafiles created by the app, used to save a datafile that was opened earlier, with the same name; and hence the file already exists on disk (the common situation if you opened for example a Word file, makes some changes, and selects Save from the File menu).<BR>
System: OSX4<BR>
- first I create some temporary file name (let's say "tName")<BR>
- next I rename the file on disk (let's say "fName") to "tName"<BR>
- next I save the file from the app as fName, setting the filetype to my app's creator and file type 4 character strings.<BR>
- finally I delete file tName<BR>
Works perfectly! Except...<BR>
If the file is at the start up disk, and I try to reopen the file (with the filetype to correct four character code of course), it's disabled (grayed). Actually, creator and filetype are all question marks. If the file is at any other place (another hard disk, the desktop, a folder on the startup disk), no problem; not grayed and creator and filetype have the correct characters.<BR>
Stated simple: if the file is at the startup disk, the creator and type become question marks; if it is anywhere else, creator and type codes are correct. A save procedure without replacing ('save as') always yields correct creator and filetypes.<BR>
Anybody any idea?<BR>
<BR>
Wil Dijkstra</FONT>
</P>
</BODY>
</HTML>