Hi,

It isn't really feasible to fix bugs in old versions so really I agree with Joe that upgrading both mojoPortal and Form Wizard Pro is the best solution, though you will need to make corresponding changes in your skin after upgrading.

There was a bug in old versions of Form Wizard where deleting results from one form instance was causing orphans in other instances. That specific bug was deleting incorrect rows from the sts_WebFormResponseSet table so the orphans would be found by

SELECT * FROM sts_WebFormResponse WHERE
[ResponseSetGuid] NOT IN (SELECT [Guid]
FROM [dbo].[sts_WebFormResponseSet]

The stored procedure that caused the problem was fixed in version 0.0.2.4 of Form Wizard. The procedure changed from this:

CREATE PROCEDURE [dbo].[sts_WebFormResponse_DeleteByForm]

/*
Author: Joe Audette
Created: 2008-09-26
Last Modified: 2008-09-26
*/

@FormGuid uniqueidentifier

AS

DELETE FROM [dbo].[sts_WebFormResponse]
WHERE
[ResponseSetGuid] IN (SELECT ResponseSetGuid
FROM [dbo].[sts_WebFormResponseSet]
WHERE FormGuid = @FormGuid)

to this:

ALTER PROCEDURE [dbo].[sts_WebFormResponse_DeleteByForm]

/*
Author: Joe Audette
Created: 2008-09-26
Last Modified: 2011-03-29
*/

@FormGuid uniqueidentifier

AS

DELETE FROM [dbo].[sts_WebFormResponse]
WHERE
[ResponseSetGuid] IN (SELECT [Guid]
FROM [dbo].[sts_WebFormResponseSet]
WHERE FormGuid = @FormGuid)

Hope that helps,

Joe

No, mojoPortal 2.3.4.8 is from July 2010, that is very old.

The System Requirments tab on the Form Wizard product page shows that Form Wizard 0.0.2.4 required mojoPortal version 2.3.6.4.

There is simply no way to get all bug fixes other than upgrading.

You could use the select statement I provided to get the current orphans and you could run the alter procedure statement to possibly fix the problem that caused the orphans but that is about as much as you can do short of upgrading.

Hope that helps,

Joe