is there a bug with the export/importing objects to .txt ?

dabatla

I have a problem that is really giving me a headache, so if somebody can help I would really appreciate it.

I'm trying to renumber a lot of objects in my database, but that is irrelevant to my problem. The problem is that when I export the objects that I want to renumber, and try to import them again, I get the following error message : "'Begin' should come here"

Now this doesn't make any sense, When I thought that I did something wrong with the renumbering, I exported it to .txt again and imported it into a new database WITHOUT changing ANYTHING in the exported file.I then got the same error message.
I also tried removing the problem object from the database, this seems to work, but then I get another error a bit later on.

I spent the last hour looking at the code of that object and I am confident that the problem isn't in the object itself as for the following reasons :
* When I exported it as a .fob and imported it back again with the .fob everything works fine.
* Everything compiles perfectly

My only conclusion is that either I made some kind of mistake(which i'm confident I didn't) or that under certain conditions either the export or import functions has a bug in them.

I'm using Navision 3.70

Thanx

Edward_Bloomfield

Hello

One possibility occurs to me - Is a) one or more of the obejcts a table? and b) are there any '//' marks in the Description column of the table designer? We have found that this causes problems on importing & exporting as text and put a rule in our documenation procedures that we never put // in this column.

Just a guess...

dabatla

It seems that it was exactly that, at least one of the bugs..... there also was a local record variable with the same name as a field name, this isn't supposed to cause any problems, but when we changed the name of the field, everything started working perfectly.

So everybody, it seems like we found a bug!
=D>

kine

There is one another bug, but with the // too... if you use somewhere the property ValuesAllowed and you want to allow / character, you need to fill // there (it is range /../ - see on-line help) the import will represent this like comments and the rest of line is not processed... (syntax error)