Sage 100

I am exporting using Visual Integrator. The client is already running several imports from VI so I decided to use this method as apposed to a report to file (hung from the menu). I am trying to assign a runtime temporary field and then using this as a condition for the export. The default value on the temporary fields is always used (as if the runtime assignment is not processed till after the export is run). Is this true? Should I just give up on the VI export and set the process up as a crystal job or a excel query?

How about assigning the field or using a ""calculation"" instead of a runtime

I am exporting from AR_customer. The client wants to pull customer balances and each time choose whether to pull 30 days and over, 60 days and over, etc...

Hi Larry, I've rarely had good luck with run time selection on VI Exports. I have spent multiple hours on it because it ""should"" work, then did a crystal report (which you can also hang off the menu) or an excel query. For exporting to file formats through Crystal, we commonly install the Sabre Logicity Crystal Report scheduler and writer app. It enables you to run the crystal report and automatically export it to the designated file type and location. I usually add that as a link in the my tasks menu or to the custom button bar. That would require each user running this to have Logicity installed on their workstation. I find it a handy tool for simple automation needs.

Larry with the conditional nature of what you're trying to do it's not gonna work with VI Export. Go with Crystal or Excel. Then if you want to automate the export there are several tools like Logicity, Visual CUT, etc.

Learned long ago that VI exporting was just too frustrating. Taught myself how to do Excel queries and have never regretted that decision. VI for importing, Excel for exporting. Teach the end power user how to use Excel queries and EVERYONE will be happier!

But make sure they are on a current version of excel. Just had a case where the data selected in the query was over 100,000 records. But the user had Excel 2003 which maxes out at 65,000 records. They complained the query wasn't working....

@ClarkWalliser , 2003 called and they want their Excel back... @JeffSchwenk , I agree I normally setup an excel query (because of the formatting and puts the user in their final destination) or a crystal report (just because on the menus which feels more integrated to the client) but in this case the client was already using VI for several integration points to their dbase program (I know 1998 is calling for that back) and thought it would be best to use VI. Off to build an alternate solution....

Remember, Larry. If everything worked, we wouldn't be working...

I am not complaining... I do wish it worked better. I would rather get paid to make things work better than to fix the things that should JUST work.

@LarryBradford - Amen!!!!