The Forums on slxdeveloper.com are now retired. The forum archive will remain available for the time being. Thank you for your participation on slxdeveloper.com!
|
| |
|
Re: Ok, strange one. comma in attachment file names
Posted: 31 Jan 07 9:37 AM
|
fiogf49gjkf0d David,
What version are you working with? As a general biz rule, I ask my users to not use 'special' characters when naming any files for SLX. ( , * ' + = - & % / \ " ) Also, even if SLX parses it correctly - SQL may not. You need to use routines for both. i.e.: a double up routine such as IF single quote char found '' .
MailMerge
Literature Request
Library Documents
Attachments
c  |
|
|
|
Re: Ok, strange one. comma in attachment file names
Posted: 31 Jan 07 10:23 AM
|
fiogf49gjkf0d We are on SLX 6.2.5 and SLX works perfectly. The problem is an ASP.NET interface. I wrote a quoting system inside SLX for our company. The quotes are exported into our Accounting package once approved and then our contract system, document imaging system, etc. I have been asked to enhance our intranet lookup to include the SLX documents. Most of the 4 plus gig of attachments work. But a few hundred of them give a 404 file not found error. I know the rights to the attachments is not the problem. I am sure that the problem is in how the path is encoded (for special characters). At first I thought it was the double commas giving me grief. Then I found some files with 2 commas that work. If I could ID what is giving me the issue I could write a function to do the (conversion). For example notice in (!QXI5VA00051APBEN01826%20Roscoe%20Ready%20Mix,%20SO#58138, CB Conv.pdf) that it did not encode the ", CB Conv.pdf" portion. On some it changes the comma to %2c and others it leaves the comma and I have some with %2c that open and some with , the still open. I will explore the SQL question this afternoon and see if I can determine anything wrong on that end. |
|
|
| |
| |
|
Re: Ok, strange one. comma in attachment file names
Posted: 31 Jan 07 2:14 PM
|
fiogf49gjkf0d The filesystem itself has special characters it doesn't allow. The OLE DB Provider has special characters it doesn't allow, and SQL has special characters it doesn't allow. Another wrench in the spoke is that you have to pass things like '' when using a single quote in SQL for it to store correctly. This is just to get attachments playing nice in the sales client. I'm sure ASP.NET adds it's own layer to the mix somehow. Things like the encoding of the page may throw off how "," is being handled. You may have to debug in such a way that you can eliminate SQL, the filesystem, the client, and then ASP.NET until you figure out which tier the problem is in.
Are these attachments added through a custom coded routine or via the client? Custom routines are easier to fix than the client but I believe v7 allows you to change how attachments are processed. If that's true then you should be able to correct the problem if it lies with the client. A SQL, filesystem, or ASP.NET issue can generally be resolved in code so it should be fixable but the issue is going to be figuring out exactly what's causing it. |
|
|
| |
|
Re: Ok, strange one. comma in attachment file names
Posted: 01 Feb 07 2:58 AM
|
fiogf49gjkf0d Id check another special character in the URL - if you cant access the file via a direct URL typed in the browser then its likely nothing to do with ASP.Net - Im not sure how it will treat # symbols - i noticed that in the first file you were trying to open at the start of this thread... |
|
|
| |
|