Hi all

I have a small database hosted on a fairly old Mac (G4 tower with 512 of
ram) and I am trying to copy zip files (all around 85mb) to container
fields. it seems to take ages. a good five mins to copy in then a few mins
when you click in the field and a few more clicking out. is this unavoidable
or are there ways to improve this.

I understand it could be various reasons (network speed, cache for the
database that sort of thing) but just wondered if any one had a pearl or two
of wisdom they could share

my machine is xp filemaker 8.5v3 and the server is upto date as well

Thanks
Craig

"cw" <c (AT) nodomain (DOT) con> schreef in bericht
news:dfidnRzAz4IBHfPbnZ2dnUVZ8t-nnZ2d (AT) bt (DOT) com...
never intended to store such amounts of data. It might be a good way to
distribute all files that you need, but I would strongly suggest to
reconsider. Filemaker has to store these data somehow and for all actions
space has to be made, as well as Data-integration-translation-verification
has to take place. Buying a screemer for a computer might help, but I still
wouldn't count on it.

Keep well, Ursus

"Ursus" <ursus.kirk (AT) wanadoo (DOT) nl> wrote

I was worried about that

is there any way to link the files in the container field to a shared folder
for the web to get to but only the users I want to

the database (db1) basically stores a copy of another database (db2) that
our clients buy, depending on what they buy dictates what is in their copy
of db2, so I don't want clients accessing other clients copies.

any thoughts?

Thanks
Craig

the database is hosted through instant web publishing for our clients

files. File one is allways distributed and is allways the same. It is
referenced to a second file that has a different layout and contents for
each distribution. And the solution is built in such a way that you can swap
file two around and it would still work.

OR

you have a one file solution that is the result of a copy of a motherfile.

The first is very vulnarable and difficult to protect.

The second is very easy to protect. Just set up access and privileges for
every user and let access to layouts and fields be governed by this. Very
easy to hide certain fields or to empty calculations using the current
account.

BUT

I must say it not entirely clear what exactly your setup is, what you store
in your file(s) and how the zips are now part of you distribition process.

Keep well, ursus

"Ursus" <ursus.kirk (AT) wanadoo (DOT) nl> wrote




sorry I will try to explain it a bit better

we currently have one large database that we enter various market data into
(market shares, trends, forecasts and values)

clients who buy our market data would normally get a cut down version of our
database (in runtime)containing just the data they bought.

now we used to send these out on a cd to all our clients but this took a
very long time. to make up all the cd,s (burning, case printing)

so now I have created a second database (client library) where we put a
zipped runtime in to a container field and allow clients to access this
database through iwp, they have passwords setup so they can only see records
that match their username, and ultimately download a zip copy of their
database.

hope that helps

the original problem was that it took ages to copy the zipped runtimes into
the database (client library) and I wondered if there was a way to link the
files somewhere where access could be limited to specific clients/usernames

In article <DbSdncV365c6rezbnZ2dnUVZ8vSdnZ2d (AT) bt (DOT) com>
"cw"<c (AT) nodomain (DOT) con> wrote:

with just a calculated download link displayed in IWP?
Matt


--
I'm trying a new usenet client for Mac, Nemo OS X.
You can download it at http://www.malcom-mac.com/nemo

In article <nemoThu061407010838 (AT) news (DOT) verizon.net> Matt
WIlls<Im (AT) Witz (DOT) End> wrote:

Come to think of it, would it not make even more sense to export the
client's data to a text file, have them download that and import it
into their copy of the runtime, instead of repeatedly downloading the
entire populated runtime?
Matt

--
I'm trying a new usenet client for Mac, Nemo OS X.
You can download it at http://www.malcom-mac.com/nemo

made for the end-user. Then create an import routine in this. Then export
the data you want to export and let the client run the import routine. Would
be much smaller as well.

Keep well, Ursus

"Ursus" <ursus.kirk (AT) wanadoo (DOT) nl> wrote

The export routine would be fairly hefty to do as there are quite a few
(50+) tables and around 40 clients who all order different parts

this is really a short term solution as I am hoping to be able to setup
remote application with the windows 2008 server for our clients and have one
copy with password restricted access.

Thanks
Craig