'Invalid Characters' validation

Hi,
I've got a form that I have managed to validate using the dreamweaver 'tag inspectors'. What I want to do though is validate one of the text fields so that users can't type in spaces etc.
I can post either the form code or the php if needed.
Thank you.

Read only textarea:
HTML:
<textarea name="read-only-text" cols="20" rows="2" readonly="readonly">Lorem ipsum dolor sit amet, consectetur adipiscing elit.</textarea>
Nancy O.
Alt-Web Design & Publishing
Web | Graphics | Print | Media Specialists
http://alt-web.com/
http://twitter.com/altweb

Similar Messages

The File name property is not valid. The file name is a device or contains invalid characters

I have an SSIS task that has run successfully for years. They just moved the dtsx to a new server and now it is failing.
Issue:
The task has a data flow that writes a raw file destination. It then has a subsequent data flow that reads the raw file destination.
The path and name of the raw file is passed to each of the data flows via the same variable.
The raw file resides in a folder on the server in the same path that the dtsx resides in.
The task fails with the "The File name property is not valid. The file name is a device or contains invalid characters" error when trying to access the raw file.
What we have done to troubleshoot:
1. I ran the task successfully on my local machine so it is definitely a server issue.
2. The first thing we were seeing was that it failed trying to write to the raw file. The task is set to "Create Always".
3. We saw that the dba's copied over the entire directory structure from the old server which included a previously created raw file, so we deleted the raw file.
4. We reran the task and it successfully wrote a new raw file but then failed on reading the raw file with the same error as above.
5. We reran the task AGAIN and this time it failed trying to write the raw file throwing the same error as above.
6. The dba looked at the directory and the account that performs the task has full control.
7. The dba looked at the raw file that was created and verified that the account that performs the task has full control of the file and that it is the owner of the file.
Summary:
The task fails when trying to access the file EXCEPT when the file does not exist. In that situation it can write the file but subsequently fails in accessing it again.

Hi Whalensdad,
Based on my research, the issue can be caused by the following reasons:
There are some invalid characters in the File name at package runtime. In this scenario, just as Russ said, could you please post the value that is in the File name variable? Also use a Script Task with Messagebox.show to show the variable values at runtime.
May be it changes to others at run time.
The account runs the package not having access to all the folders in the path. Since you are moving the dtsx file from one server to the current server, do you also move the raw file to the same folder in the current server? Does the user runs the package
have access to all the folders in the path? To solve this, please ensure that the user has access to all folders and the raw file in the path on the current server.
Thanks,
Katherine Xiong
If you have any feedback on our support, please click
here.
Katherine Xiong
TechNet Community Support
Please see the response above. I can't use a message box on a server so I logged the values to the database. The resource account has full control to the folder. I haven't been able to get the DBA to check the SQL Agents permissions, but I was always under
the impression that if you use "Run As" on the task, it will not use the SQL Agent but the account you identify it to "Run As". The "Run As" account has full control on the folder and file.

The file name is not valid. The file name is a device or contains invalid characters.

Hi ,
I am getting below error in SSIS 2008 package when it is run through control-m
The file name is not valid. The file name is a device or contains invalid characters.
component "FF_SRC_InboundFidelityInputFile" (1) failed the pre-execute phase and returned error code 0xC020207E.
although this package is working fine in dev environment from visual studio.
control-m agent has proper permissions to the folder still it is failing. Please if anyone knows solution for this issue. I am working on this issue since more than a week but reached nowhere. Please help.
Thanks
Paras Gupta

Hi Paras,
Based on your description, it is not the VS IDE issue, if it is related to the SSIS, I suggest you post the issue in this forum here:http://social.msdn.microsoft.com/Forums/sqlserver/en-US/home?forum=sqlintegrationservices
, and there you would get better response.
Best Regards,
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.

Word cannot open this document. The document might be in use, the document might not be a valid Word document, or the file name might contain invalid characters (for example,\ /).

I recently upgraded to a new Macbook Air running Lion, from my 2007 white Macbook running Snow Leopard. I had Office for Mac 2004 on the 2007, but had to upgrade to Office for Mac 2011 to be compatible with Lion on the Air. Now when I try to open my documents on the Air that were saved under Office 2004 on the old computer, I get the following message: Word cannot open this document. The document might be in use, the document might not be a valid Word document, or the file name might contain invalid characters (for example,\ /).
Any suggestions? Thank you.

Ha,ha,ha.....I figured it out. But for anyone else who's having this problem, it seems that while Office 2004 allowed dates in this format: 00/00/00, Office 2011 doesn't like it at all. I just changed the format in the document names to 00-00-00 and all is well. Documents are opening beautifully!

Value 'KIRBYu00A0' of characteristic 0SORTL contains invalid characters

hello experts!
i am facing this error while activating 0vendor. data not available either in info object master neither in psa.
Error Message: Value 'KIRBY ' (hex. '004B004900520042005900A0') of characteristic 0SORTL contains invalid characters
Message no. BRAIN060
Diagnosis
Only the following standard characters are valid in characteristic values by default:
!"%&''()*+,-./:;<=>?_0123456789ABCDEFGHIJKLMNOPQRSTUVWXYZ.
Furthermore, characteristic values that only consist of the character # or that begin with ! are not valid.
You are trying to load the invalid characteristic value 1. (hexidecimal representation 004B004900520042005900A0).
Procedure for System Administration
Try to change the invalid characters to valid characters.
If you want values that contain invalid characters to be admitted into the system, make the appropriate setting in BW Customizing. Refer to the documentation describing the requirements for special characters and the possible consequences.
For more information on the problems involved with valid and invalid characters, click here.
regards
vijay

Hi Vijay,
after KIRBY is a characteristic value which cannot be interpreted by BW properply / is not in the valid char list.
KRIBY is hex value 004B0049005200420059
the invalid char is hex value 00A0 -> online hex converter didn't found a ASCI match.
To solve the problem you will need to fix the record in the source. Or you go to PSA -> delete all in teh field and re-enter KRIBY.
Best regards,
Axel

Renaming files with invalid characters in their names on NTFS partitions, introduced by operating systems other than Windows

Essentially, Linux created some files with colons (:) in the name on a NTFS partition where I have Windows installed. I have since uninstalled Linux, but now I can only view these files in Windows Explorer. I can't open them, I can't even rename them to
correct the problem. It's as if they don't exist, because of the invalid search paths.
If I try to rename them in Windows Explorer I get following message.
The file name you specified is no valid or too long.
Specify a different file name.
Well isnt' that something?... isn't that nice? Windows is able to display these files, but it doesn't allow me to open them and it certainly doesn't like me to rename them. So why is it whining about it then, when I'm trying to help? It says "try a different
file name". Yeah, right! Like I haven't tried that one already! It doesn't matter what file name I input it will never accept it.
So what am I supposed to do now? Ditch Windows and go back to Linux? Surely, Microsoft doesn't like the sound of that. Sure, I could reinstall Linux or run a Linux live system to correct the problem. But what good is Windows then? I might as well switch to
Linux altogether.
After doing some research I now know by fact that it's (kind of) possible to rename files from UNIX and UNIX-like operating systems to those compliant with Windows by using something called file name character translation. To some level this is essential and
necessary for Windows interoperability with other operating systems (Windows is not the only operating system in the world). But this seems to be very complicated and I can't get my head around it. My brain is in overload. I don't know where to start.
Once there was a...
There's the Windows Services for UNIX (SFU) 1.0, 2.0, 3.0, 3.5. The first two versions were based on MKS Toolkit, a package licensed by Microsoft from MKS Inc. The later versions were based on the similar Interix product, after Microsoft purchased the company
that made it.
Then there's the new Subsystem for UNIX-based Applications (SUA). These are services for UNIX components. They are supposed to have Client for NFS v3 included as well. But the server components from the SFU line is missing (e.g. Server for NFS). These are included
in Server editions of Windows.
Then there's the Microsoft Knowledge Base article
289627: "How to Enable File Name Character Translation". This article seems to describe exactly my situation.
Windows and UNIX operating systems have restrictions on valid characters that can be used in a file name. The list of illegal characters for each operating system, however, is different. For example, a UNIX file name can use a colon (:), but a Windows
file name cannot use a colon (:). If a UNIX user attempts to create a file with a Windows illegal character on a Windows Services for UNIX network file system (NFS) share, the attempt is unsuccessful and the UNIX client computer receives an input or output
error.
It goes further than that. At first glance, this KB article also seems to offer a solution to this exact problem, with examples as shown below.
For example, the following maps the UNIX colon (:) to a Windows dash (-):
0x3a : 0x2d ; replace client : with - on server
I checked these values in charmap.exe and they are correct. Except for 2D not being a "dash", it's rather a hyphen ("hyphen minus" to be exact), but these two have pretty much the same appearance and they get interchanged a lot, I'm sure
they are used to it by now. (Yes, the characters! They don't mind.)
Then there's this registry key.
HKEY_LOCAL_MACHINE\Software\Microsoft\Server For NFS\CurrentVersion\Mapping
Well, of course, I don't have Server for NFS. So this is a dead end. Well, actually, it was a dead end from the beginning...
1. First of all, I'm not working with a network share on a NAS or SAN storage. The files are on the local disk drive where Windows is installed, so that's a DAS for you.
2. I don't have SFU! Well obviously, I'm on Windows Vista! So that means SUA!
3. SUA are service components only. No server components. Can you guess what that means? Yeah... no "Server for NFS" since it's a server component.
4. Windows Vista is a client side operating system! Server for NFS is only offered for use with Windows Server systems.
5. Back to square one!
So there you have it. They all lived happy for the rest of their lives...
I'm stuck here. Can someone tell me what to do? I mean beyond the obvious option to use Linux to fixa a Windows problem? The NTFS file system itself supports colons in file names. It's Windows that doesn't, and so by default it proclaims it invalid character.
Surely, even a Windows client operating system like Windows Vista should be able to allow the user to at least rename files with invalid characters to something more sensible (from the system point of view) and valid, if not being able to open them as they
are. Just add some crazy voodoo code to it and it will work. If you can make it possible on Windows Server with UNIX user-mode subsystem on NT kernel, then what's stopping you from giving the Windows client system the same benefit?
So what now? Purchase a Windows Server 2012 R2 license, copy my invalid files to a NAS share with NFS on a UNIX or Linux system, and have a go at the Windows registry and Server for NFS? Yeah... you're right, it's probably a bit over the top...
On a second thought... I might as well install Linux again. There are countless situations where Linux has helped me solve problems related to, and more often than not caused by Windows.

Essentially, Linux created some files with colons (:) in the name on a NTFS partition where I have Windows installed. I have since uninstalled Linux, but now I can only view these files in Windows Explorer. I can't open them, I can't even rename them to
correct the problem. It's as if they don't exist, because of the invalid search paths.
If I try to rename them in Windows Explorer I get following message.
The file name you specified is no valid or too long.
Specify a different file name.
Well isnt' that something?... isn't that nice? Windows is able to display these files, but it doesn't allow me to open them and it certainly doesn't like me to rename them. So why is it whining about it then, when I'm trying to help? It says "try a different
file name". Yeah, right! Like I haven't tried that one already! It doesn't matter what file name I input it will never accept it.
So what am I supposed to do now? Ditch Windows and go back to Linux? Surely, Microsoft doesn't like the sound of that. Sure, I could reinstall Linux or run a Linux live system to correct the problem. But what good is Windows then? I might as well switch to
Linux altogether.
After doing some research I now know by fact that it's (kind of) possible to rename files from UNIX and UNIX-like operating systems to those compliant with Windows by using something called file name character translation. To some level this is essential and
necessary for Windows interoperability with other operating systems (Windows is not the only operating system in the world). But this seems to be very complicated and I can't get my head around it. My brain is in overload. I don't know where to start.
Once there was a...
There's the Windows Services for UNIX (SFU) 1.0, 2.0, 3.0, 3.5. The first two versions were based on MKS Toolkit, a package licensed by Microsoft from MKS Inc. The later versions were based on the similar Interix product, after Microsoft purchased the company
that made it.
Then there's the new Subsystem for UNIX-based Applications (SUA). These are services for UNIX components. They are supposed to have Client for NFS v3 included as well. But the server components from the SFU line is missing (e.g. Server for NFS). These are included
in Server editions of Windows.
Then there's the Microsoft Knowledge Base article
289627: "How to Enable File Name Character Translation". This article seems to describe exactly my situation.
Windows and UNIX operating systems have restrictions on valid characters that can be used in a file name. The list of illegal characters for each operating system, however, is different. For example, a UNIX file name can use a colon (:), but a Windows
file name cannot use a colon (:). If a UNIX user attempts to create a file with a Windows illegal character on a Windows Services for UNIX network file system (NFS) share, the attempt is unsuccessful and the UNIX client computer receives an input or output
error.
It goes further than that. At first glance, this KB article also seems to offer a solution to this exact problem, with examples as shown below.
For example, the following maps the UNIX colon (:) to a Windows dash (-):
0x3a : 0x2d ; replace client : with - on server
I checked these values in charmap.exe and they are correct. Except for 2D not being a "dash", it's rather a hyphen ("hyphen minus" to be exact), but these two have pretty much the same appearance and they get interchanged a lot, I'm sure
they are used to it by now. (Yes, the characters! They don't mind.)
Then there's this registry key.
HKEY_LOCAL_MACHINE\Software\Microsoft\Server For NFS\CurrentVersion\Mapping
Well, of course, I don't have Server for NFS. So this is a dead end. Well, actually, it was a dead end from the beginning...
1. First of all, I'm not working with a network share on a NAS or SAN storage. The files are on the local disk drive where Windows is installed, so that's a DAS for you.
2. I don't have SFU! Well obviously, I'm on Windows Vista! So that means SUA!
3. SUA are service components only. No server components. Can you guess what that means? Yeah... no "Server for NFS" since it's a server component.
4. Windows Vista is a client side operating system! Server for NFS is only offered for use with Windows Server systems.
5. Back to square one!
So there you have it. They all lived happy for the rest of their lives...
I'm stuck here. Can someone tell me what to do? I mean beyond the obvious option to use Linux to fixa a Windows problem? The NTFS file system itself supports colons in file names. It's Windows that doesn't, and so by default it proclaims it invalid character.
Surely, even a Windows client operating system like Windows Vista should be able to allow the user to at least rename files with invalid characters to something more sensible (from the system point of view) and valid, if not being able to open them as they
are. Just add some crazy voodoo code to it and it will work. If you can make it possible on Windows Server with UNIX user-mode subsystem on NT kernel, then what's stopping you from giving the Windows client system the same benefit?
So what now? Purchase a Windows Server 2012 R2 license, copy my invalid files to a NAS share with NFS on a UNIX or Linux system, and have a go at the Windows registry and Server for NFS? Yeah... you're right, it's probably a bit over the top...
On a second thought... I might as well install Linux again. There are countless situations where Linux has helped me solve problems related to, and more often than not caused by Windows.

Invalid Characters shown in UTF-8 character set

There is an XMLP report whose template output character set is ISO-8859-1. The character set ISO-8859-1 is required for this report as per Spanish Authorities. When the report is run, output gets generated in the output directory file of application server. This output file doesn't contain any invalid characters.
But when the output is opened from SRS window, which opens it in a browser, the invalid characters are shown for characters like Ñ , É etc.
Investigation done:
Found that the output generated on the server is having ISO encoding and hence doesn't contain any invalid characters. Whereas the output generated from SRS window, it is in UTF encoding, so it seems the invalid characters are displayed when conversion takes place from ISO to UTF-8 format.
Created the eText output using the data xml and template using BI publisher tool, the output is in ISO encoding. So if i go and change the encoding to UTF-8 by opening it in explorer or Notepad++, invalid charcters are shown for Ñ, É etc.
Is there any limitation, that output from SRS window will show only in UTF-8 encoding? If not then please suggest.
Thanks,
Saket
Edited by: 868054 on Aug 2, 2012 3:05 AM
Edited by: 868054 on Aug 2, 2012 3:05 AM

Hi Srini,
When customer is viewing output from the SRS window, then it contains invalid characters because it is in UTF-8 character set. Customer is on Oracle OnDemand so they cannot take the output generated on the server.Every time they have to raise a request to Oracle for the output file. So the concern here is, why don't the output from SRS window show output with valid characters ?
The reason could be conversion of ISO format to UTF-8. How could this be resolved ? Does SRS window output cannot generate in ISO format ?
A quick reply will be appreciated as customer is chasing for an update.
Thanks,
Saket
Edited by: 868054 on Aug 7, 2012 11:08 PM

Dynamic column Name# Contains Invalid Characters. Bind_table() fails

Hi WD experts,
I have tried to use the bind_table() on a dynamically generated table. Now it happens that this dynamic table contains columns like NAME# . This gave rise to a dump :
The Name NAME# Contains Invalid Characters. Valid Characters are A-Z, 0-9, _, and /.
Other tables which do not have such columns are correctly bound.
In my method , I first loop over the field catalog to retrieve some field names from a dynamicallt generated report...
LOOP AT lt_fieldcat_out INTO lwa_fieldcat.
    comp-name = lwa_fieldcat-fieldname.
    comp-type ?= cl_abap_typedescr=>DESCRIBE_BY_DATA( lwa_fieldcat-FIELDNAME ).
    APPEND comp TO comp_tab.
ENDLOOP.
structure which represents the dynamic table
struct_type = cl_abap_structdescr=>get(
                                          p_components = comp_tab
                                          p_strict = abap_FALSE   ).
node_info = wd_context->get_node_info( ).
node_info = node_info->add_new_child_node(
                              name        = 'DYN_TAB_NODE'
                              IS_MANDATORY                 = ABAP_TRUE
                               IS_MANDATORY_SELECTION       = ABAP_FALSE
                               IS_MULTIPLE                  = ABAP_TRUE
                               IS_MULTIPLE_SELECTION        = ABAP_FALSE
                               IS_SINGLETON                 = ABAP_FALSE
                               IS_INITIALIZE_LEAD_SELECTION = ABAP_FALSE
                              static_element_rtti = struct_type
                              is_static = abap_false
struct_type = node_info->GET_STATIC_ATTRIBUTES_TYPE( ).
Afterwards, I bind a dynamic table to the new node...
Do you have an idea how to circumvent this ?
Thank you,
cheers,Zied.

cols have to be changed

How to delete trailing spaces or invalid characters

Hi experts,
I am loading data into a DSO. But in the activation it is showin error. Data is coming upto New data table. After that it is showing error as:
=============================================
Value 'Eversafe ' (hex. '204576657273616665 ') of characteristic 0CUSTOMER contains invalid characte .
Diagnosis
    Only the following standard characters are valid in characteristic
    values by default:
    !"%&''()*+,-./:;<=>?_0123456789ABCDEFGHIJKLMNOPQRSTUVWXYZ.
    Furthermore, characteristic values that only consist of the character #
    or that begin with ! are not valid.
    You are trying to load the invalid characteristic value Eversafe &
    (hexidecimal representation 204576657273616665 ).
System Response
Procedure
Procedure for System Administration
    Try to change the invalid characters to valid characters.
    If you want values that contain invalid characters to be admitted into
    the system, make the appropriate setting in BW Customizing . Refer to
    the documentation describing the requirements for special characters and
    the possible consequences.
===========================================
After i edit this in psa it is showing another record as error.
I think we have to delete the trailing spaces. If this is the case anyone please provide me how to write routine in the transfer rules to delete the trailing space.
Full points will be assigned.
Thanks & Regards,
V N.

Hi Venkat,
Thanks for your reply.
How can i know what are the extra invalid characters to be permitted.
And also i am getting a message while activating the DSO as follows:
============================================
Activation of M records from DataStore object ZDSO_OO3 terminated
Process 000033 returned with errors
=============================================
Please help me to solve this issue.
Thanks & Regards,
V N.

PCG Seed Data Invalid characters displayed in FRC

Hi, I'm not certain this is the correct forum or not.
Customer has PCG 7.3.2 on 11i, using FRC.
Many menus and concurrent program names & messages (all seed data) that use accents, are displaying garbled characters.
eg: GRC Controls : RÃ¨gles associÃ©es aux Ã©crans
when viewed through TOAD, Data looks the same, yet non PCG seed data with same words have the correct french accented characters.
NLS character set is WE8ISO8859P1, not UTF8. (which is standard in 11i FRC installs).
As per the PCG install guide, I have tried using both files (for UTF8 & WE8ISO8859P1) in $ORACLE_HOME/forms60/admin/resource/FRC, but the results do not change.
I think this may have had something to do with environment setting used during the installation process.
I would like to experiment with this, but cannot find the scripts/files that actually seed the FRC data for seeded menus and concurrent programs.
Can anybody guide to to these ? or provide an alternative or known (I can't find one) solutiuon ?

Hi Srini,
When customer is viewing output from the SRS window, then it contains invalid characters because it is in UTF-8 character set. Customer is on Oracle OnDemand so they cannot take the output generated on the server.Every time they have to raise a request to Oracle for the output file. So the concern here is, why don't the output from SRS window show output with valid characters ?
The reason could be conversion of ISO format to UTF-8. How could this be resolved ? Does SRS window output cannot generate in ISO format ?
A quick reply will be appreciated as customer is chasing for an update.
Thanks,
Saket
Edited by: 868054 on Aug 7, 2012 11:08 PM

Accepting invalid characters

Hi,
Here we had a field that the users can enter any thing and any language and they want to report on that.
Tried entering values in RSKC. But i can not enter in RSKC every time there is invalid char. Is there a option at the infoobject level taht we can select . So that it wont check for validity and generate sid out of that . So we can do reporting on the field.
Thanks,
Ravi.

Hi,
As a long term you can apply some user exit in source system side or change your update rules to ensure that this field is getting blanked out before getting loaded in cube or add that particular char to permitted character list in BW (Run TCODE RSKC
Input the <character> and execute the program) This will add <character> to the allowed characters list.
OR
RSKC --> type ALL_CAPITAL --> F8 (Execute)
OR
Go to SE38 and execute the program RSKC_ALLOWED_CHAR_MAINTAIN and give ALL_CAPITAL or the char you want to add.
Check the table RSALLOWEDCHAR. It should contain ALL_CAPITAL or the char you have entered.
Refer
/people/sap.user72/blog/2006/07/23/invalid-characters-in-sap-bw-3x-myths-and-reality-part-2
/people/sap.user72/blog/2006/07/08/invalid-characters-in-sap-bw-3x-myths-and-reality-part-1
/people/aaron.wang3/blog/2007/09/03/steps-of-including-one-special-characters-into-permitted-ones-in-bi
http://help.sap.com/saphelp_nw04/helpdata/en/64/e90da7a60f11d2a97100a0c9449261/frameset.htm
Thanks,
JituK

Error message if invalid characters entered in PM order oper.short text fld

Hi ALL,
I need to display a error message, when user enters the invalid characters in work order operation short text field. The error message should be displayed during work order u201CSaveu201D (during creation and change mode).
Kindly let me know is there is any user exit / BADI can be used for this.
Note: I have checked some user exit, such as IWO10009 but I am not getting the value of Operation short text (AFVGD-LTXA1) to compare and throw the error message
Regards
Ramu

hi
the exit is correct but don't use structure field,
follow this to get text
get AUFPL(Routing number of operations in the order)from CAUFV and paa it in AFVC -AUFPLyou get the short text
it can be usefull
-ashok

Discoverer Report showing invalid characters in the report data

Hi,
Can you please help me. I have designed a discoverer report in discoverer desktop 4i, when it is running the data showing some invalid characters in the data like below.
kara¿ah L¿MAK HOLD¿NG A.¿
I have executed the same query in sql plus at that time the data shows correctly. Please let me know, is there any settings required.
Best Regards,
Umamaheshwar.

Hi Umamaheshwar
This could be a registry setting. Let me give you some background. In the Windows registy, every Oracle Home has a setting called NLS_LANG. This is the variable that controls, among other things, the numeric characters and the language used. The variable is made up of 3 parts. These are:
language_territory.characterset
Notice how there is an underscore character between the first two variables and a period between the last two. This is very important and must not be changed.
So, for example, most American settings look like this: AMERICAN_AMERICA.WE8MSWIN1252
The second variable, the territory, controls the default date, monetary, and numeric formats and must correspond to the name of a country. So if I wanted to use the Greek settings for numeric formatting, editing the NLS_LANG for Discoverer Desktop to this setting will do the trick:
AMERICAN_GREECE.WE8MSWIN1252
Can you please check your settings? Here's a workflow:
a) Open up your registry by running Regedit
b) Navigate to HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE
c) Look for the Oracle Home corresponding to where Discoverer Desktop is installed. It's probably called KEY_ORANT
d) Clicking on the Oracle Home will display all of the variables
e) Take a look at the variable called NLS_LANG - if it is correct Exit the registry
f) If its not correct please right-click on it and from the pop-up select Modify
f) Change the variable to the right setting
g) Click the OK button to save your change
h) Exit the registry
Best wishes
Michael

PHP MYSQL and DW Question: Invalid characters and new lines entry/viewing

Hello all,
I have followed David Powers' two php/dw/mysql books and I've
set up PHP
pages that insert, edit, delete, etc. listings. Everything
works fine
except for invalid characters being inserted into the
database, and then
displaying with a question mark in firefox.
Is there a trick to cleaning up the data that a user may
paste into a
textbox on a web page for insertion in the database before
the data is
inserted or as it is inserted? Em dashes, en dashes, 'curly
quotes' etc.
are giving me problems.
Also, when I enter new lines into the php page while I'm
typing out
information for a record, these new lines are not being
displayed either
in the database (using phpmyadmin to view) or on the
resulting details
pages, even though I'm using nl2br, etc. Is there a way to
make this
work reliably?
Thank you for any help you may give me!
-John

Hello all,
I have followed David Powers' two php/dw/mysql books and I've
set up PHP
pages that insert, edit, delete, etc. listings. Everything
works fine
except for invalid characters being inserted into the
database, and then
displaying with a question mark in firefox.
Is there a trick to cleaning up the data that a user may
paste into a
textbox on a web page for insertion in the database before
the data is
inserted or as it is inserted? Em dashes, en dashes, 'curly
quotes' etc.
are giving me problems.
Also, when I enter new lines into the php page while I'm
typing out
information for a record, these new lines are not being
displayed either
in the database (using phpmyadmin to view) or on the
resulting details
pages, even though I'm using nl2br, etc. Is there a way to
make this
work reliably?
Thank you for any help you may give me!
-John

Invalid characters error while ODS activation

I have 2 queries regarding Invalid characters
1) I got following error while activating ODS.
Value 'HYDERABAD - IV COMMISSIONERATE ' (hex. '48594445524142414420<b>2D</b>204956A020434F4D4D495353494F') of characteristic ZEXCRG contains     invalid characters
   I added space (ALT+255) in RSKC as suggested in other threads and activated the ODS.('-' is already there in RSKC).
Above record did not give any error but got the same error for another record.
Value 'SURAT II ' (hex. '535552415420<b>96</b>204949 ') of characteristic ZEXCRG contains invalid characters
   Can anybody tell me why there is difference between in representation(HEX) of same char and which char should I add to RSKC to solve the error?
2) RSKC_ALLOWED_CHAR_GET lists the space as default allowed char, so why do I need to add the same again?

Hi Vikram:
go to RSKC: do a ALL_CAPITAL. then do the permitted charcters in BW(do a F1 and copy all and paste). also, please be advised that add <b>~</b> (tilda) and take a closer look at the error you got and insert that there.
hope it should fix the issue.
assign points if helpful
kalyan

'Invalid Characters' validation

Similar Messages

Maybe you are looking for