Skip to main content
Participating Frequently
April 28, 2008
Answered

Broken Recordset

  • April 28, 2008
  • 7 replies
  • 364 views
Broken Recordset:
I have created a Form with a table that includes 15 textfields and a recordset that polls data based on a login page. I have mapped specific fields from the database to return the data under the textfields that are labeled First Name, Last Name, ID, and 13 other informational fields. The login page only asks the users for their First Name, Last Name and an ID which corresponds to the recrdset I have created. When a user logs in only 6 of the fields are populated by the recordset and the rest are blank when their is data in all fields in the database. Now here is the strange thing..If i copy the recordset and rename it and then map another field or two that were not populating from the original recordset, that field or two now shows up. So I can get all fields to populate by creating multiple recordsets, I have created up to SEVEN duplicate Recordsets to get all the info to populate.
This is a big issue as this is a View page and the recordset paging can only be linked to ONE recordset so only some of my data shows when users page/scroll through the records.
It almost sounds like a memory buffer issue in Dreamweaver Recordset code.
Has anyone experienced this issue and is there a resolution?
This topic has been closed for replies.
Correct answer Newsgroup_User
MBaron007 wrote:
> My recordset has the following statement:
> "SELECT * FROM FanExperience WHERE EmployeeID = ? AND FName = ? AND LName = ?"
>
> In the actualy recordset the TYPE for FName and LName is TEXT and the Database
> TYPE is CHAR. The EmployeeID is Numeric for both.
> I have re-ordered so the numeric is first and the Text types are last in the
> sql query and the same result.
> Do I need to move the actual database fields of type text to the bottom on the
> database?

Yes, the database fields with a datatype of TEXT needs to be the last
ones. I don't know how it will handle 2 of them, I guess your about to
find out. You may be able to just change the order of the columns by
selecting them in your select statement. Don't use *, just list the
columns in the order you want them, it might work, not 100% but may give
you a quick indication.

Steve

7 replies

Inspiring
April 29, 2008
MBaron007 wrote:
> Thanks Steve. I had to list out each and every database field (all 118 of
> them) in the recordset and listed the TEXT Datatypes last in the order that
> they appear in the form.
> Thank you very much for your help!
>
> --Marc
>

Hi Marc,
You should only need to list the ones you are going to display or use,
but I am glad its now working for you.

Steve
HawksITAuthor
Participating Frequently
April 28, 2008
Thanks Steve. I had to list out each and every database field (all 118 of them) in the recordset and listed the TEXT Datatypes last in the order that they appear in the form.
Thank you very much for your help!

--Marc
Newsgroup_UserCorrect answer
Inspiring
April 28, 2008
MBaron007 wrote:
> My recordset has the following statement:
> "SELECT * FROM FanExperience WHERE EmployeeID = ? AND FName = ? AND LName = ?"
>
> In the actualy recordset the TYPE for FName and LName is TEXT and the Database
> TYPE is CHAR. The EmployeeID is Numeric for both.
> I have re-ordered so the numeric is first and the Text types are last in the
> sql query and the same result.
> Do I need to move the actual database fields of type text to the bottom on the
> database?

Yes, the database fields with a datatype of TEXT needs to be the last
ones. I don't know how it will handle 2 of them, I guess your about to
find out. You may be able to just change the order of the columns by
selecting them in your select statement. Don't use *, just list the
columns in the order you want them, it might work, not 100% but may give
you a quick indication.

Steve
HawksITAuthor
Participating Frequently
April 28, 2008
My recordset has the following statement:
"SELECT * FROM FanExperience WHERE EmployeeID = ? AND FName = ? AND LName = ?"

In the actualy recordset the TYPE for FName and LName is TEXT and the Database TYPE is CHAR. The EmployeeID is Numeric for both.
I have re-ordered so the numeric is first and the Text types are last in the sql query and the same result.
Do I need to move the actual database fields of type text to the bottom on the database?
Inspiring
April 28, 2008
MBaron007 wrote:
> Steve,
>
> Thanks for your reply. I am using a SQL 2000 database.
> The datatypes are char, text, datetime and numeric.
> There are 8 char , 2 datetime, 2 text and 2 numeric columns.
> I have tried only mapping the char fields with no luck.
> Any thoughts?

Text is where your problem lies, you might want to read up on it, but
basically its a binary column, and does not get stored in the same place
as the others, so when you have a recordset with the type text included
it has to be the last column in your recordset, otherwise you get
nothing out of the following columns.

Steve
HawksITAuthor
Participating Frequently
April 28, 2008
Steve,

Thanks for your reply. I am using a SQL 2000 database.
The datatypes are char, text, datetime and numeric.
There are 8 char , 2 datetime, 2 text and 2 numeric columns.
I have tried only mapping the char fields with no luck.
Any thoughts?
Inspiring
April 28, 2008
MBaron007 wrote:
> Broken Recordset:
> I have created a Form with a table that includes 15 textfields and a recordset
> that polls data based on a login page. I have mapped specific fields from the
> database to return the data under the textfields that are labeled First Name,
> Last Name, ID, and 13 other informational fields. The login page only asks the
> users for their First Name, Last Name and an ID which corresponds to the
> recrdset I have created. When a user logs in only 6 of the fields are
> populated by the recordset and the rest are blank when their is data in all
> fields in the database. Now here is the strange thing..If i copy the recordset
> and rename it and then map another field or two that were not populating from
> the original recordset, that field or two now shows up. So I can get all
> fields to populate by creating multiple recordsets, I have created up to SEVEN
> duplicate Recordsets to get all the info to populate.
> This is a big issue as this is a View page and the recordset paging can only
> be linked to ONE recordset so only some of my data shows when users page/scroll
> through the records.
> It almost sounds like a memory buffer issue in Dreamweaver Recordset code.
> Has anyone experienced this issue and is there a resolution?

Nothing to do with memory, more than likely due to your data types. What
database are you using? What data types for each column are you using?

Steve