Recent content by HHUK

Very true, I think even if there is code you can copy and paste, type it out manually. Just so it sticks into your head, one time I copy and pasted some code and went back and thought "ohh.. what's this?" :D Do jump right in though, try a few tutorials. Eventually you'll need to start planning...

Hold down the shift key, then doubleclick your .mdb file. Keep the shift key held down while the database is opening so it registers it properly. Your bars should now be there. I notice that if it takes a while to open and you let go of the shift key before it's fully opened it can carry on...

s1police is correct, goto Tools, then startup. You can disable the menus, etc. So only your startup form will show when you turn it on. Then the are only permitted to follow your database as you wish. You could protect this further by compiling the user's copies into .MDE's but always keep a...

Asamalaycum, I think you need to look at your databases abit. Students is fine at the moment. Teachers/Subject repeat each other abit. I would do: Students table Subjects table Lessons table The Students data you have is held in students. Subjects contains subjectID, subject name and...

Ah, well I guess I'm stuck at the same point as you. Looks like programming a web based front-end could be difficult. I would imagine ASP/ASP.net would be one thing to look into as I've seen it recommended on a few forums.

I'm in the same boat. I would like to try upscale but I'm not sure what to use as a front-end if I do. I've read you can use an Access front-end to connect to an SQL Server which may be good news for you. It's using an ADP file rather than an MDB...

How many users do you have roughly? Once you go above 20 people using it simultaniously then it's worthwhile going the web way anyway, their technologies are more used to having that many users and won't get corrupted as easily. Access features an upsizing wizard which can help you get your...

My database is based on clients. The only possible repeated information is: Nationality Religion Ethnicity Support Worker Support Type Diagnosis Almost everything else is pretty unique, I guess I'm blessed with a good set of data to work on. I have tables with lists of these possible repeated...

Hey guys, I was just wondering, do you all see normalisation as mandatory? I spent months on it in college, it was drilled into my head. Early on in my latest project I was setting up all the tables to make it normalised, I did abit of tinkering and got carried away, forgetting about...

I'm by no means a pro, I'm an IT Technician turned office guy who deals with all the databases. In my job for making and maintaining I earn £10 p/h but if I were to do it freelance I would probably charge a one off fee, try work out how long you'd spend on each form and report, add up a time...

You could import all those databases into a big, new database. Tidy it all up, give all the forms a common theme making it all look professional. Split it to a front-end/back-end system and work that way. Run the user level security wizard and make usernames/passwords for everybody. Then you...

Sorry, I realised that mistake after I had posted it.

The first one: The jet engine which powers Access should handle that sort of situation, I've tried breaking my own database by opening it from different PC's and trying to input data at the same time but it seems to handle it well. I believe it only starts to screw up if you have quite a large...

Hey JaredNJames, It's possible to move the back-end and then re-link them. If you go onto the tables tab in the objects menu. (Not quite sure of the official name, it's the thing that usually opens on startup of access) you'll see all your tables have a little blue arrow next to them, this...

(In Access 2003, might be worded differently in other versions) I would goto Tools -> Database Utilities -> Database Splitter This would create a front-end and a back-end... the front-end would be the forms, simply an empty shell. The back-end would be your database tables, queries, etc. I'll...