VoiceGuide IVR Software Main Page
Jump to content

Database Not Working

Recommended Posts

Sir Good Day, see my attached script and database. The script not taking the data from the database

what do you think the problem?Im Using Access2007 and VG 6.0v

 

Attached:

0509_1213_vgEngine.zip

Share this post


Link to post

In your SQL query one of the fieldnames is the same as one of the reserverd keywords. You can try putting brackets around the FieldName in the SQL queries, but it's best to just change the database's column names to not use a reserved keyword for any of the columns.

 

In your case the table CIdlanguage has a column named: Langauage

 

Change the column name to soemthing else (eg: CallersLang) and amend the SQL queries in the script appropriately.

Share this post


Link to post

Alos the SQL query in module VehicleData is wrong. The $RV is missing an end bracket

 

Right now you have:

 

SELECT VehicleBrand, VehicleType, VehicleColor, ExpireDate, Email1 FROM (AccountFile) WHERE DriverID=$RV[GetDriverNumber;

 

change

 

$RV[GetDriverNumber;

 

to

 

$RV[GetDriverNumber];

Share this post


Link to post
In your SQL query one of the fieldnames is the same as one of the reserverd keywords. You can try putting brackets around the FieldName in the SQL queries, but it's best to just change the database's column names to not use a reserved keyword for any of the columns.

 

In your case the table CIdlanguage has a column named: Langauage

 

Change the column name to soemthing else (eg: CallersLang) and amend the SQL queries in the script appropriately.

 

Good Day Sir, what do you mean the same as one of the reserved keywords? May I know Sir what fieldname you mention. By the way

Thanks because I forgot to put bracket.

Share this post


Link to post

the table CIdlanguage has a column named: Langauage

 

Change the column name to something else (eg: CallersLang) and amend the SQL queries in the script appropriately.

 

Langauage is a reserved word.

Share this post


Link to post

You can try putting brackets around the FieldName in the SQL queries.

 

ie: replace

 

Language

 

with:

 

[Language]

 

wherever you see Language in your SQL queries.

Share this post


Link to post

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×