dbaccess to Wingz

Looks like I posted my last question too quickly. I believe I worked something out. I was trying to take the results of a selecte statement from dbaccess or ISQL and pull it into a Wingz sheet. Two problems occurred. The output was not TAB delimited and the columns retrieved were pulled in one per line when the total width of the column went over 80 characters. The best solution I can find so far involves letting the user develop the query as he wants, then adding 'unload to "filename"' above the query when done. This eliminates the problem of the columns coming out vertically arranged instead of across horizontally . . . But unload has undocumented restrictions and will not save in a TAB delineated format. I got a Tech support Bulletin from Wingz (evidentally they get this call a lot). Their kludge to pull in a | delimited or space delimited file is a kludgy horror! I relies on each line to be pulled in being less than 255 characters too . . . Anyways, my simple solution for now is to let the user unload the data from dbaccess, then from Wingz open a sheet, select a file and my program will shell out to unix, run a simple awk script to convert all |'s to TAB's and then use APPEND to pull the converted file in . . . That's my solution so far . . . Anybody else have any ideas? As for Informix, I would appreciate it is they allowed TAB's in dbaccess and for a line size greater than 80 characters too . . . How many people running unix with X really stick with 80 character!?!?!?! Second, I asked for an extended APPEND command in Wingz so a programmer could specify the delineator, TAB of course being the default. This seems like their best bet for the Wingz users . . . <sigh> Isn't it fun being the one to hit all of these problems and to put in the requests . . . I'll probably be done with the entire project and the next major revision of it before I see the changes . . . Oh well. That's what programmer get paid for I guess . . .