Hello Group,

 

Happy New Year to all … hope it’s a great one for all of you.

 

Due to a recent change that Bruce Conrad and I agreed to make on MD7 – the
database that stores the data deployed by his CGI scripts at
www.knowmexico.com – I want to report a glitch in the data export/import
function of the Built-In Short Reports.

 

I changed an A12 Field to an A12A1 field on a Panel so we could store a
variable length text field to be used to display a video link as we plan to
start deploying video from the website.

 

As you all know, in order to change a Panel, all of that Panel’s data has to
be exported. I’ve always used the Built-In Short Reports to create a
PANELx.GET file to import the data. I had never had a problem with this
scheme before.

 

What now causes the problem is using accented letters; i.e. Bucerías instead
of Bucerias … Cihuatlán instead of Cihuatlan. The ñ also acts strangely. In
some cases it is ignored, in others the record is lost.

 

Fortunately, the damage was not major. The Panel contained 185 records.
Importing the .GET file resulted in 175 records. The missing ones all
contained an accented vowel or an “ñ”.

 

Some of the recovered records were mis-spelled; i.e. “Bahía Kino” landed as
“Bahino” breaking down-line links. Editing “Bahino” using DP’s keyboard
mapping function to “Bahía Kino” restored all the links.

 

I believe Google and other search engine’s algorithms take care of these
diacritical mistakes.

 

However, how can we fix this in the DP Export/Import Reports?

 

Love to all,

Tony 

 

 

 

 

 

 

 

All the best,

Tony

 

Tony Perez

Co-Founder & Managing Director

Know & Enjoy Mexico

 <http://www.knowmexico.com> http://www.knowmexico.com

 

Cellular: 415-828-7212

 

_______________________________________________
Dataperf mailing list
[email protected]
http://lists.dataperfect.nl/mailman/listinfo/dataperf

Reply via email to