Database in Excel?

[YNWA]

Hi,

I have someone asking for a relational database but it needs to be build using Excel due to bugets blah de blah.

Now as good as I am in Excel, I have never done this before. Always Access.

Can anyone help me out where to start with this and are there any templates available that sort of cover the structure etc..?

See attached a spec document I have been given...

If this was Access it would be a simple job consisting of a weeks work to get the basics there. With Excel I am not sure how to quote for the job as it could be complicated or straightforward? Any ideas?

Thanks

 

[bob fitz]

I don't mean to be rude but perhaps you should read the doc that you posted a little more carefully. The first line of the "Summary" says

This needs to be MS Access (or a free alternative)

 

[YNWA]

I don't mean to be rude but perhaps you should read the doc that you posted a little more carefully. The first line of the "Summary" says

I know but that's changed now apparently and they simply have to have it in Excel as no one has Access.

Thinking on the fly, could I build an Access database and just allow them to have It locked down running on Runtime Access?

 

[Mihail]

What about a free platform as Open Office ?

 

[Galaxiom]

I know but that's changed now apparently and they simply have to have it in Excel as no one has Access.

Excel is a spreadsheet. It is not practical to use it as relational database. The should be the end of the story as far as they are concerned.

Yes it is possible to build a database in Excel. Hell, it is even possible to do it in Word and hold all the data in text files. Everything can be done in recordset loops. But, and it is big but, such constructions are generally a waste of effort for the developer when the right tool makes the job easy.

Doing something for free can put unreasonable load on the developer because the client puts zero value on every aspect of the project including the developer's time so they are prepared to consume any amount of it so save themselves the smallest cost.

Thinking on the fly, could I build an Access database and just allow them to have It locked down running on Runtime Access?

That is what is normally done.

 

[YNWA]

Thanks and just to confirm that I can use runtime and they will be able to access that runtime file on multiple pc's that do not have Access of anykind on it?

 

[bob fitz]

Thanks and just to confirm that I can use runtime and they will be able to access that runtime file on multiple pc's that do not have Access of anykind on it?

If you intend to use this app on a network with multiple users then it should be split in to a back end and front end. Each user will need a copy of the front end and runtime installed. Each front end would then need to be linked to the tables in the back end.

 

[Alansidman]

Here is a very good link on the subject of Access Runtime.

http://www.hitechcoach.com/

Scroll down about 1/3 of the way for a detailed explanation of what you need to do.

 

[YNWA]

If you intend to use this app on a network with multiple users then it should be split in to a back end and front end. Each user will need a copy of the front end and runtime installed. Each front end would then need to be linked to the tables in the back end.

So I create the DB in full Access.

Then if I need to split it, how do I go about that if they only have runtime?

 

[bob fitz]

You could try this:
Use the wizard to split the db. Copy the new back end file to a shared folder on the network. Open the new front end db and create a link to the back end db. Then put a copy of the front end on each users machine.