You might want to check out this thread for a similar situation...

http://www.lantica.com/Forum3/cgi-bin/yabb2/YaBB.pl?num=1292685347/0

Steve

Well, I thought I had it working...

If there is one record in the subform, calling RunExportSpec or performing a manual export, will create one record in the txt file and the import works fine. If there are two or more records in the subform, RunExportSpec, or manual export will create as many parent records as there are entries in the subform, in the txt file. All the data from the subform does get listed in the txt file. When you run an import, you get as many new records as there are subform entries, each containing one line of the subform data.

Of course, I only want one record containing all of the subform data.

I hope I was clear enough on this, any help would be appreciated, thanks.

Here's the code:

var vSpec as String
var vFile as String
var vRun as Int
var vNav as Int


	vRun = @LoadExportSpec("ExportRefRecord")
	If vRun = 1
	{
		RunExportSpec("Docs\ExportRef.txt",",","",0,1,0,1,0,1,0,0) //RunExportSpec("Docs\ExportRef.txt",",","",0,1,0,1,0,1,0,0)
	}


vNav = @SelectTreeItem(@Application + "!Forms!Add Data!Reference!Reference")

@exit
 

Hi Ray,

That must have been the trouble, I couldn't see where the export didn't match the import so I started over from scratch and it works fine now, thank you.

Just curious, when looking at the txt file, is it normal for it to show as many record entries as there are subform entries?

Thanks for all of your help & have a Merry Christmas,

Brandon

Thanks for the explanation,

Brandon

I've continued to occasionally have further troubles with exporting and importing.  I believe I have found the culprit. One of the LE's is a text editor field. At times some of the data within this field contains a comma. When you run the export/import the comma(s) change either the export or import spec and then you get more than one copy of the original, depending on how many subform line items contain data.

I dreamed up the code below to change any commas to dashes

var vNotes as string

vNotes = @Replace(Customernotes, ",", " - ")

Customernotes = vNotes

Formcommit("Ledger")

Formcommit("reference") 

which runs before this code:

vRS = @FormFieldValue("reference", "Ref", 0)

vNav = @SelectTreeItem("Search Update Menu!Search (F7)")

Ref = vRs

vNav = @SelectTreeItem("Search Menu!Search Commands!Retrieve New Results (F10)")


	vExp = @LoadExportSpec("ExportRefRecord")
	If vExp = 1
	{
		RunExportSpec("Docs\ExportRef.txt",",","",0,1,0,1,0,1,0,0)
	}
	ClientLocalValue("ImportRoutine", 1)
	vNav = @SelectTreeItem("Search Update Menu!Navigation!Switch to Add Data Mode (Ctrl-F6)")
	@Exit 

to remove the commas first. This works OK accept that when there is also an equal "=" sign in the text field, the process stops before "Search Update Menu!Navigation!Switch to Add Data Mode (Ctrl-F6)" can take effect and lands me back to my main menu.

I'm not sure if any other characters could cause trouble with the export/import spec.

Is there a way to tell sesame to disregard any special characters within this field or any other solution?

Thanks.

Thank you very much Steve, can't thank you enough. I guess I'm not focusing well enough at times. I should have thought about the ability to change the separator but it never crossed my mind.

I tried several different separators and ended up using a pipe "|".  Could there be any negatives in using the pipe?

RunExportSpec("Docs\ExportRef.txt","|","",0,1,0,1,1,1,0,0)

This works beautifully.

Merry Christmas,

Brandon

OK, I'll do that, good advice.

Upon further testing, with using all the symbols except the pipe, there still is one, or a combination of them, that are causing the trouble. However, the majority of the data within those fields are using more of the standard symbols such as , : $ ! () = + - and those do not appear to be causing any trouble.

Thanks again,

Brandon