Home » questions » Creating dictionary with Access?

Creating dictionary with Access?

4
2006-07-30 04:11:07, Category: Programming & Design
I want to put a bilingual dictionary on my website. Do you think it's feasible to do it with Access? Would one or two tables work fine? And, should I learn SQL so that people can look up words from my website? Thanks a lot I already have MS Access. What I think is to prepare my dictionary on my hard disk, and once it is ready to publish it. I can upload that Access file and access it through ADO or MySQL, right? Because, I think it can be easier to prepare the dictionary on Access, rather than creating each entry by MySQL, am I right?

Answers

  1. Acidedge

    On 2006-07-30 09:33:31


    SQL would be the best way to go about this. It is also extremely easy to learn. A bi lingual dictionary would probably have more records in it than Access will allow, it only allows a limited amount of records. Plus, Access is pretty naff compared to SQL

  2. mixturenumber1

    On 2006-07-30 14:39:21


    nope. try mysql it is opensource so its free. you will need a scripting language like php to query the database. if you need to do it for free try www.ning.com it allows you to create phpscripts and I think they give you database space . also have you thought about using XML? sorry if you have access already try it out on that and see how you get on.

  3. hswes

    On 2006-07-30 04:55:06


    I would suggest SQL. At first Access is quite limited with the recordsets and is also rather slow. You need at least three table, becourse you need a many to many relationship so you need one table for language one, one table for language two and one table fot the many to many relation to create a sophisticated lookup Helmut

  4. Prateek Saxena

    On 2006-07-30 04:22:22


    You see man if you use MS Access you will be able to put in on your web page but for someone to view that dictionary they would need to have a particular ActiveX programm or a specific .DLL . I would suggest you use SQL or try out AJAX