Super slow export off found set

[falkaholic]

Hi,

I have a problem exporting records. I have a simple(ish) invoicing database that has a customer and line items database. After I do a search in a line items field in a certain date range, I export the customer postal code and the line item name and ID. It's super slow, it could 1 record per hour if I let it go. If i choose and randam records and export them it's completed instantly, but with records found in a range its goes super slow. Anyone know whats going on?

[falkaholic]

Hi,

I have a problem exporting records. I have a simple(ish) invoicing database that has a customer and line items database. After I do a search in a line items field in a certain date range, I export the customer postal code and the line item name and ID. It's super slow, it could 1 record per hour if I let it go. If i choose and randam records and export them it's completed instantly, but with records found in a range its goes super slow. Anyone know whats going on?

[falkaholic]

Hi,

I have a problem exporting records. I have a simple(ish) invoicing database that has a customer and line items database. After I do a search in a line items field in a certain date range, I export the customer postal code and the line item name and ID. It's super slow, it could 1 record per hour if I let it go. If i choose and randam records and export them it's completed instantly, but with records found in a range its goes super slow. Anyone know whats going on?

[MoonShadow]

Hi Eric,

I had a large export take 3 hours when I first started using 7. I finally figured out that I was exporting fields based upon a different TO than from the layout I was currently on and/or that TOs closest relationship. As soon as I selected the correct fields, it was done in 5 minutes. Another time, I was finding on a Contact field but, instead of the Contact TO directly related, I had selected a Contact TO that was related by/thru several other relationships. Again, it took forever.

A possibility (because it happened to me). POV (point of view) is everything in FM7 and you can get somewhere the direct route - or go to Australia to get to California if you're not careful.

[MoonShadow]

Hi Eric,

I had a large export take 3 hours when I first started using 7. I finally figured out that I was exporting fields based upon a different TO than from the layout I was currently on and/or that TOs closest relationship. As soon as I selected the correct fields, it was done in 5 minutes. Another time, I was finding on a Contact field but, instead of the Contact TO directly related, I had selected a Contact TO that was related by/thru several other relationships. Again, it took forever.

A possibility (because it happened to me). POV (point of view) is everything in FM7 and you can get somewhere the direct route - or go to Australia to get to California if you're not careful.

[MoonShadow]

Hi Eric,

I had a large export take 3 hours when I first started using 7. I finally figured out that I was exporting fields based upon a different TO than from the layout I was currently on and/or that TOs closest relationship. As soon as I selected the correct fields, it was done in 5 minutes. Another time, I was finding on a Contact field but, instead of the Contact TO directly related, I had selected a Contact TO that was related by/thru several other relationships. Again, it took forever.

A possibility (because it happened to me). POV (point of view) is everything in FM7 and you can get somewhere the direct route - or go to Australia to get to California if you're not careful.

[MoonShadow]

Sorry Eric, I didn't notice this was for vs. 5. Besides, if what I suggested was true (in vs. 7), it wouldn't work instantly for random records then but would rather respond about the same ... doggy-slow.

Maybe it's attempting to re-sequence them ... like based upon a summary (Summarize By)? Or maybe try compressing all three files? Are you sorting the relationships? Or is the unsorted state of LineItems by this date (ascending)? It's obvious I'm stabbing in the dark, huh ...

[MoonShadow]

Sorry Eric, I didn't notice this was for vs. 5. Besides, if what I suggested was true (in vs. 7), it wouldn't work instantly for random records then but would rather respond about the same ... doggy-slow.

Maybe it's attempting to re-sequence them ... like based upon a summary (Summarize By)? Or maybe try compressing all three files? Are you sorting the relationships? Or is the unsorted state of LineItems by this date (ascending)? It's obvious I'm stabbing in the dark, huh ...

[MoonShadow]

Sorry Eric, I didn't notice this was for vs. 5. Besides, if what I suggested was true (in vs. 7), it wouldn't work instantly for random records then but would rather respond about the same ... doggy-slow.

Maybe it's attempting to re-sequence them ... like based upon a summary (Summarize By)? Or maybe try compressing all three files? Are you sorting the relationships? Or is the unsorted state of LineItems by this date (ascending)? It's obvious I'm stabbing in the dark, huh ...

[gdurniak]

There is no reason to be super slow off a found set. However, it IS possible you have some corrupt records. Try exporting ALL records to a "merge" file, then import back into a clone

[gdurniak]

There is no reason to be super slow off a found set. However, it IS possible you have some corrupt records. Try exporting ALL records to a "merge" file, then import back into a clone

[gdurniak]

There is no reason to be super slow off a found set. However, it IS possible you have some corrupt records. Try exporting ALL records to a "merge" file, then import back into a clone

[BobWeaver]

If your export includes unstored calculation fields, especially ones that use aggregate functions or summary functions, this can slow things down dramatically.

[BobWeaver]

If your export includes unstored calculation fields, especially ones that use aggregate functions or summary functions, this can slow things down dramatically.

[Oldfogey]

or go to Australia to get to California if you're not careful.

You'd never get there because you'd just stay in Australia!

(Yes, I know. Sorry. .... Not really.)

[Oldfogey]

or go to Australia to get to California if you're not careful.

You'd never get there because you'd just stay in Australia!

(Yes, I know. Sorry. .... Not really.)

[falkaholic]

thanks for the tips guys.

i'll will try the clone and import way. The tech support guy already said he tried recovering it. There isn't any summary fields.

thnx again, i'll hate maintaining old pre 7 systems.