Database integration

[halfpixel]

Hello, I'm sure this is a trivial question for most of you, but I'm in a hurry and need to be sure about something.

I have a website redesign project and the client needs to integrate a database to the site. This database was done by another company but for some reason they are not providing any support to the client. Anyway, this database is an additional feature, not needed for the rest of the site. So, I would like to propose to the client to go ahead with the redesign and leave the database integration for later, until we find a programmer who can handle this (I'm a designer, not a programmer).

I guess that eventually we can put a link to the database interface and do any necessary customization to integrate it visually with the rest of the site.
Does it sound like a good idea? Would you recommend a different approach?

Any thoughts will be greatly appreciated. Thanks!

 

[halfpixel]

Thanks for your reply amenzl. According to the little information I have about this database, it was developed in ASP.NET 2, and has never been used. I don't even know if it has ever been installed in a server (which I assume should be necessary), or where it lives right now. The purpose of this database is to allow the members of an association to check certain credit history of individuals, so, as I said, I think that eventually this feature can be added to the website as a new section, just a button to link to the database interface. Is that right?

 

[halfpixel]

Ok, I have a meeting later today with the client and hopefully I'll get a better idea of what's going on with this database. For now I feel more confident about promoting the redesign, regardless of the database status. I'll post the results of the meeting later. Thanks again amenzl!