Enterprise - help!

[James Rea]

> The Initialize starts by calling a procedure which runs importusing  
> and the error comes up immediately.
> 
> The importusing is fetching an up-to-date batch of info from a text  
> file on our network server.
> 
> Is there a list anywhere of what things a shared database can't do?  
> Is importusing one of them? And how does one work around this?

I don't think that importusing should be a problem in a shared database.

Does your procedure do a removeunselected? That's a no-no.

We're kind of flying blind here. You might post the entire source of the
.Initialize procedure, then it might be obvious.

Also, if you open the .Initialize procedure you should be able to step
thru it and see exactly where the error occurs. Another possible help
would be the Error Detail wizard -- have you enabled it? This allows you
to press the More Info button when an error occurs. That often allows
you to pinpoint the source of a problem quickly.

Jim Rea

---------------------------------------------------------------------
---   Celebrating 30 years of software excellence (1978-2008)     ---
---------------------------------------------------------------------
ProVUE Development          (714) 841-7779
18685-A Main Street PMB356  http://www.provue.com/
Huntington Beach, CA 92648  Panorama: Turn information into knowledge
---------------------------------------------------------------------