Microsoft access database

25 views
Skip to first unread message

Fadi

unread,
Oct 18, 2009, 1:00:48 PM10/18/09
to WebVelocity
Hi,

I'm new to WebVelocity, and I'm trying to test it using a Microsoft
Access database, which is included as a database platform, but I was
not able to find information on how to configure this connection.

Can anybody help me?

Thanks,

Fadi Mansour

James Robertson

unread,
Oct 18, 2009, 1:19:01 PM10/18/09
to webve...@googlegroups.com
For the connect string, use the path to the access file. Username and
passwd should not matter

Fadi Mansour

unread,
Oct 18, 2009, 1:27:10 PM10/18/09
to webve...@googlegroups.com

Thanks, I'll try it.


I thought I would have to configure some ODBC connection or something.


Regards,


Fadi Mansour

James Robertson

unread,
Oct 18, 2009, 1:31:57 PM10/18/09
to webve...@googlegroups.com
Mm, I think you might be right.  I was thinking of the SQLLite connection.  Go ahead and configure the ODBC connection and use that name

Fadi

unread,
Oct 19, 2009, 6:32:01 AM10/19/09
to WebVelocity
I did, but pressing "Test login" gives me back "Database not
configuered".

I tested both with and without a username. When no name is supplied,
the field is highlighted with red.

Any other suggestions, or where can I look to find out what's
happening?

Regards,

Fadi Mansour

unread,
Oct 21, 2009, 6:01:48 AM10/21/09
to WebVelocity
After delving a little deeper into this problem I found out this error
message:

'[Microsoft][ODBC Microsoft Access Driver] Could not find file ''d:
\fadi\WebVelocity\INFORMATION_SCHEMA.mdb''.'

I found this using the debugger after an exception when trying to open
the schema.

The question is: Do I have to put my database file in a specific
location? Or is this a bug?

Thanks,

Fadi

James Robertson

unread,
Oct 21, 2009, 6:36:16 AM10/21/09
to webve...@googlegroups.com
Do you have an access database set up when you try this?

Fadi Mansour

unread,
Oct 21, 2009, 6:47:12 AM10/21/09
to webve...@googlegroups.com
Yes I do, the database is in another folder that that in the error message, and there's an ODBC user DSN named 'testfadidb'.

In the database definition I used this 'testfadidb' as the address.

I have even tried accessing this database using Glorp directly, and it workded. I could login and execute SQL commands with no errors.
Reply all
Reply to author
Forward
0 new messages