I design on a Powerbook G3 running FM5 Dev. The related databases run beautifully whether I simply compress them and send the archive out to a coworker with full version FM5 or bind them to a runtime. The glitch comes when Windows users request the same files. Transfering them, via TCP/IP is no problem. I have access to a desktop running Win98 and FM5 Dev. They open without problem and I systematically tweak some of the scripts and adjust some layouts to be more Windows friendly. Everything in the folder looks the way it should before I bind to the runtime on Windows and use Suffit for Windows to create an .exe archive (still no sign of unusual files or folders). My problem arrises when the user unstuffs the archive, opens the solution folder and discovers, among the multitude of .dll files, that there's also a resource fork folder. Where did it come from and why is it popping up? Any ideas on what I need to do to the db, to make Windows accept it as its own, before archiving? Could file names be too long? Would a nonWindows friendly script create this resource fork? I know its a Mac to Windows issue but how do I correct it without completely reconstructing the 5 file db on the Windows side?

quote:

---

Originally posted by tmac:

I design on a Powerbook G3 running FM5 Dev. The related databases run beautifully whether I simply compress them and send the archive out to a coworker with full version FM5 or bind them to a runtime. The glitch comes when Windows users request the same files. Transfering them, via TCP/IP is no problem. I have access to a desktop running Win98 and FM5 Dev. They open without problem and I systematically tweak some of the scripts and adjust some layouts to be more Windows friendly. Everything in the folder looks the way it should before I bind to the runtime on Windows and use Suffit for Windows to create an .exe archive (still no sign of unusual files or folders). My problem arrises when the user unstuffs the archive, opens the solution folder and discovers, among the multitude of .dll files, that there's also a resource fork folder. Where did it come from and why is it popping up? Any ideas on what I need to do to the db, to make Windows accept it as its own, before archiving? Could file names be too long? Would a nonWindows friendly script create this resource fork? I know its a Mac to Windows issue but how do I correct it without completely reconstructing the 5 file db on the Windows side?

---

Are you copying the entire folder from the Mac to the PC, or are you copying individual files. If you're copying the entire folder, try going with one file at a time instead.

Chuck