Classic ASP Discussion - Record display question

Print Page | Close Window

Record display question

Printed From: Web Wiz Forums
Category: General Discussion
Forum Name: Classic ASP Discussion
Forum Description: Discussion on Active Server Pages (Classic ASP).
URL: https://forums.webwiz.net/forum_posts.asp?TID=21345
Printed Date: 29 March 2026 at 2:08am
Software Version: Web Wiz Forums 12.08 - https://www.webwizforums.com

Topic: Record display question

Posted By: haxor2
Subject: Record display question
Date Posted: 19 September 2006 at 10:44pm

I am trying to write a page that displays the results of two seperate tables and the fields are listed individually for fromating reasons. The code i used is below. However, I keep getting a type mismatch response.write on certain fields in the db. I have tried many things to figure out what the problem is. I even have two fields that are defined identical in the database. Date/time and all the same options however, one displays and one does not. Any suggestions would be help. Sorry for the length of the post and thanks in advance

Set ra=Request.Form("RmaN")
Set db=Server.CreateObject("ADODB.Connection")
db.Provider="Microsoft.Jet.OLEDB.4.0"
db.Open "C:/Inetpub/wwwroot/web/posts.mdb"

set rs=Server.CreateObject("ADODB.recordset")
sql="select rmalog.*,rmaprocessing.* from rmalog, rmaprocessing where rmalog.rmanumber5=rmaprocessing.rmanumber2"
rs.Open sql,db
%>
<table border="0" width="10">

<%
'Autonumbered
%>
<%
rs.movefirst
do while not rs.eof
%>
<tr>
<td>

<%=rs("key")%>
</td>
<td>
<%
'number
%>
<%=rs("dateissued2")%>
</td>
<td>
<%
'number
%>
<%=rs("customernumber3")%>
</td>
<td>
<%
'Text
%>
<%=rs("customername4")%>
</td>
</tr>
<%
rs.movenext
loop
%>

<%
rs.close
db.close
%>
</table>
</body>

Replies:

Posted By: haxor2
Date Posted: 20 September 2006 at 3:13pm

Nevermind, looks like it was a database issue. I exported all ther records to and excel spreadsheet and reimported to access and now it works fine. Probably something about switching data types in the database after data has been entered into the field. I am not sure if this is the case but export/import seems to have fixed the problem so far.