Exporting Problem on a Mac

[bob sherman]

One of my users installed a newer version of my runtime program on his Mac and then experienced the following problem. After he imported his files into the new version he found that when he attempted to export even a single record (300KB) the export feature takes ten or more minutes and when completed, the size of the file is 5.5MB even though when you open up the exported file all you see is that single record of data. He installed the program on two different Macs and is having the problem in both locations. This problem does not occur on my Mac, which burns the disks. Any Ideas?

[Mike D.]

Bob,

I haven't seen that problem before, but I have a few questions.

1. What version OS does the user have on the Macs and what version are you using?

2. Did you create the runtime version on a PC or a Mac?

Mike

[bob sherman]

Hi Mike,

I created the program on a PC, brought it over to a Mac and developed the runtime from there. Both Macs have OS9. For two years I have been supplying updated Mac versions to my user in this manner, but this is the first time this problem has occurred. I'm now wondering if his Mac at home and school have maxed out of memory. Runtimes take about 19MB of space and he hadn't deleted his old program

Bob

[Mike D.]

Hmmm,

None of my customer have runtime, I've convinced them to buy FileMaker so I haven't had that situation. But I do know that if the hard drive is close to full you lose speed especially when the files are that large. 19MB is about 3 times the size of the copy that you gave me last month. Granted it there were minimal records, but I wasn't aware that converting a solution to runtime bloated the files that much.

Mike