Quote:
Quoting TheMadMartian:

Quote:
Quoting movie_madness:

Quote:
Quoting DarklyNoon:

Quote:

This looks amazing, do you make this available for others too?

If I shared my work with others, I would violate IMDb's terms the same way DVD Profiler would, I believe, because my tool imports heavily from IMDb.

I'm a little late to this but I don't think he meant sharing your database data, just your database design.  I use Microsoft Office but don't have the programming skills to create something this nice so would definitely be interested in the design.

Sharing my design would mean sharing how I obtain data from IMDb, which I'm also reluctant to do because the legality of doing so is also not so clear cut, due to IMDB's usage terms.

My app requires Microsoft SQL Server when it runs, so unless you have that set up at your end, you can't even open my app.  In short, my app is not easily distributable due to various reasons.  It is not designed to be distributed anyway.

To understand my design, you would need to be proficient in relational database first (which is a college sophomore-level subject).  My app and DVD Profiler are basically "database applications" that rely much on the fundamental principles of relational database, which include topics like indices, data types, data structures, referential integrity, relationship, etc.

I can give you a glimpse of what my app does by way of a video or two (here is a brief video of how my tool retrieves IMDb cast and crew).  But this is no way to show you truly what my design entails.

Quote:
Quoting ccla:

Quote:
Movie_madness,

May I ask what you use to create the interface for your DB?  I am pretty good at designing databases and sql programming,  but it’s been a while since I prigrammed a front end.  What I end up doing is using Access as a front end, but that can be limiting.  I used to use Delphi ages ago, but again not sure what is available today.


claudio

He's mentioned that Microsoft Office is required so my guess is Microsoft Access.