Please Help A Poor Teacher In The UK....

Aug 21, 2007

........... Hi, I've just come across this forum and was hoping that you can lend a hand.

I teach in a special school - our pupils are slow learners and find reading and writing rather challenging. They are slow learners. Here, we say that they have moderate learning difficulties. In most other ways, they are like any other kids - and if you met them out and about on the streets, they would not seem any different to their mainstream peers.

I teach Computer skills throughout the school, and this year, I have to teach databases to our older pupils. In the past, I confess, I have used excel to demonstrate some database capabilities, but I would like to use the proper program this time.

I purchased Access for the school - only to discover that it is Access 2007. So not only do I have to learn an unfamilar program [for me] but also it looks very different too.

Not to be outdone, I have bought one of those 'teach yourself access 2007' CDs and all is going well with that. [Though it is still early days].

What I need are some sample databases for the kids to practice sorting, filtering etc on. I have downloaded some sample databases, but they all seem very complicated to me. Simple is the key, here. Something like someone's database of cds [I did start to make one of these myself but it was very time consuming]

Or maybe some ideas of simple databases that the kids could have a go at making. That could be good. My mind is such a jumble that I can't think straight right now.

Any ideas? Can anyone please help?

Eternally grateful, in advance,

imp
x

View Replies


ADVERTISEMENT

Split DB Poor Performance?

Nov 16, 2005

:confused:

I have split my database application that was approaching the 20MB size. This I have split into a front end (approx. 8 Mb) with linked tables to a back end database (approx. 12MB).

Network is 100Mb Ethernet.

However, since doing this, end users have noticed that scrolling through records and especially running reports takes significantly longer sometimes 3x/ 4x longer. I understood that splitting the DB would have a beneficial effect from a development / application 'release' point of view and maybe if I were to create an MDE file of the front end, I could also benefit from reduced network traffic given that end users are using a compiled executable etc.

With the speed issues I have been experiencing I have had no choice but to roll back to the original application format with everything in the the one MDB file.

Has anyone else had to do the same - given similar speed degradation issues?

Thanks
Guido

View 5 Replies View Related

Sudden Poor Performance

Jan 11, 2006

Last week, my access97 db, with back end and front end, both residing on a network as they have been for the last 2 years, decided to start running at 1/4 of the speed that they usually have. The db is used by 16 users, and roughly 5 are on at any given time (Operating system - XP). Both front end and backend were compressed without any change in performance. No changes in programming or number of records was introduced as of late. Checking with our IT department indicated that the performance of the network and drive have not changed and are up to snuff. I moved a copy of the FE and BE to my hard drive and found performance to return to normal speed, although I am not sure if it always ran faster on a PC. Any experience with this irregularity and options to check would be greatly appreciated?

View 2 Replies View Related

Split Database = Poor Performance

Feb 27, 2007

So, I split up my database and housed the tables database part of the split on a shared network drive and am experimenting with the front end of the database which i've housed on my local computer. I've tried most of the recommendations: shortened the name of the db, changed fe to mde file, changed link tables to subdatasheet (none), but still my forms (only 2) are taking a while to load up. The forms are pretty substantial, and have a form and a subform on each. Can anyone offer up any recommendations to improve the speed?

View 14 Replies View Related

Best Practice To Handle Poor Data Quality In Relationships?

Jul 21, 2007

I'm attempting to normalize an enormous table with order data, but I'm running into some problems. The table currently contains many duplicates, of which also included the actual order information (yikes!), but I managed to normalize it almost all the way down. It appears that different accounts can be used on orders, and these order numbers are being recycled for some reason months down the line (don't ask my why they're reusing them for future orders because I have no idea either, they should be creating new order numbers). Of course, the Order number is the primary key in my table as it should be. I guess the same thing can occur with the sales rep. Anyway, I'm struggling to find the "best practice way" to deal with this situation. I'm almost tempted to create an intermediary "transaction table" or something like that between the main general order information (which at this point will basically be the Order Number and Customer ID only), then include a table with the account information and sales rep info, then have that link to the Order Detail with the products, quantity, order number and various dates for those order numbers. Order maybe it should be a separate, related table, but not between the general order information and the order details? Can anyone tell me if I'm on the right track for this situation? It was a total curveball that the rep and account information could be different on these orders.

Option 1:
Order (Order #, Customer) -> Transaction Information (Order #, Account Type, Sales Person) -> Order Details (dates, products, quantities, etc)

Option 2:
Order (Order #, Customer)---> Transaction Information (Order #, Account
| Type, Sales Person)
|
|-> Order Details (dates, products, quantities, etc)

View 2 Replies View Related

Poor Error Handling In Access - It's Like Going Back In Time. Anyone Agree?

Sep 22, 2005

I'm sick of the lame excuse for error messages that Access gives out.. I'm talking about 'Overflow', 'invalid use of Null' and such like.

What about telling you what field/expression caused the error and on what record if applicable.

It's so frustrating - Access obviously knows what caused the error but refuses to tell you so you have to go through the annoying process of taking out fields one by one (when in query view).

Does anyone agree that they need to make the error handling in Access much better?

Thanks for any interest in my post.

View 4 Replies View Related







Copyrights 2005-15 www.BigResource.com, All rights reserved