2. ASPRunnerPro General questions
  3. error with latest build
This topic is locked

error with latest build

 		2/15/2008 10:43:26 AM
ASPRunnerPro General questions
T
 Tim author

Hello,
I'm not sure if this is the right place for this, but I'll start here. I just downloaded the latest beta of ASPRunnerPro 5.2 (thanks Sergey). I had created a project in the previous beta version, and now when I open the project in this new version I have 2 issues:
First, on the "Edit SQL query" page, if I click on a table where i have pulled in additional tables via an INNER JOIN, the application crashes.
Second, if I "Build" the project I get the following error:
c:\Program Files\ASPRunnerPro5.2\source\include\commonfunctions.asp(108) - Couldn't find element strTableName
I guess the third issue is that none of the pages come up when I browse to them, but I assume that's related to these other issues.
Any help is appreciated.

Thanks,

Tim
Sergey Kornilov admin 2/15/2008

Tim,
please send your project folder zipped along with your database to support@xlinesoft.com.

I'll check what is wrong.
T
 		Tim author 2/15/2008

Thanks Sergey. I'm using a MS SQL 2005 database. I assume I should just create a backup of the database to send along with the project folder...?
J
 		Jane 2/19/2008

Tim,
yes.
S
 		semleon 2/21/2008

I Too am getting this error "c:\Program Files\ASPRunnerPro5.2\source\include\commonfunctions.asp(108) - Couldn't find element strTableName" .
Appears to have happend when I opened a 5.0 version of a project in the 5.2 version, added inline edit, and tried to build it. I reset all the pages so there was no residual formating from the previous version.
And now, even when I build a new project in 5.2, I get the same error message.
I've tried to reinstall ASPRunner, but did not fix.
Please help.
Sergey Kornilov admin 2/22/2008

Semleon,
make sure you use build 391.
If this doesn't help send your project folder zipped along with your database to support@xlinesoft.com.
S
 		semleon 2/22/2008

I was on 388. Looks like 391 has fixed the issue.
Thank you.