Item Numbers using Character-Number-Character

Hello,

I am having a little problem using Item numbers That begin with a character - S10046E.
When I have two products using the following:
product a; S10046E and product b; S10064F,
When I click on the product a thumbnail it takes me to product a detail page. When I click on product b it takes me to the product a detail page.
When I Take the first letter out everything works fine.
My ItemNum table is set up for varchar50.
Normally I would just take it out but I have a new manufacturer that will not be able to pull and ship product without it.

Any suggestions?

Thanks in advance,
Rob

Is the productID correct in the passed URL? This seems like very strange behavior.

How is the recordset filtered on the details page?

Ray,

The productID is passed correctly. I have a little over 100 products working fine, for some reason its these.

The recordset is filtered by:

SELECT items.*, callOut.CallOut
FROM items LEFT JOIN prodCallout ON items.ItemNum = prodCallout.ItemID LEFT JOIN callOut ON prodCallout.ProdCall = callOut.CallOutID
WHERE ItemNum= colname
ORDER BY ItemName ASC

colname:
Name: colname
Type: Integer
Default Value: -1
Runtime value: $_GET['ItemNum']

I tried to change the integer to text but I received a js error.

What a weird error!?!

Thanks,
Rob

It needs to be type text. That is the source of the problem.

Ray,

Thanks. I still get the js error when I tried to change from the integer to text (in the dialog box when I double click on recordset), but was able to make the change when I found it in the code.

Is there an issue on making changes when the pages are generated through the wizard? Along with the js error on this, I also received a js error and template locked error when trying to add a cookie (I will problably post in the cookie forum later) to form on the generated confirm page. I am still trying to work around that issue.

Thanks again!

Regards,
Rob

There is an issue with some of our server behaviors interfering with recordsets in CS4. We discovered the issue recently and you can get a fix for it by posting a support ticket.

Ray,

OK, Thanks for the info.

Regards,
Rob