Recent content by DevastatioN

I've used code that looks nearly identical to this. And yes it works (at least in Excel 2003), it exploits the way Excel passwords are stored, and will give your password as a series of A's and B's, with a symbol or other letter at the end. This password also correlates to the real password...

As stated above you should only have one table tblUsers. In this table include FName, MName, LName, Gender, Type, Username, Password. Type field should be used with a dropdown as Admin, Teacher, Pupil. You no longer need tblTeachers, tblAdmins, and tblPupils. Anytime you only need one or the...

Added both links on my personal website. You guys rock, keep up the great community!

Based on your clarifiction, I would recommend the table approach for the questions, especially since you brought another note to light. Your audit isnt really for the user and the file, it's for the file, which happens to have multiple users. If I understand this again, you could have...

If I get this correctly, you just record the username, the file number, and answers to a series of questions. Some questions that may help clarify: Do both audits have the same questions? Do both audits use the same number of questions? Are the questions always static? Or do they vary on...

You want to look at just importing all that data into the database, but if you wish to do it as you described. You need to create a new "Link Table", referencing that Excel file. In the table window, click "New", Select "Link Table" and press Ok, change the "Files of Type" to Excel and...

If you each record in the table can be accessed by only ONE person (never two people or more can access the record), then make a field in the table called UserID, or CreatedBy, AccessedBy etc, whatever name you feel is appropriate. Everytime they open the view/edit form, it must filter to show...

Design view will run slow if a linked table is being accessed by someone else (that's what I find as well anyway). If you create a persistent connection to the backend this should resolve the issue. I create a tblConnection in the backend with a single field, and a single record "dummy". When...

What is the size of the backend? What is the size of the frontend? How many records are in your biggest table? If you create a very basic report, just generic one field to list something, is it still slow to load? (Try the report on frontend, AND try on the backend too, see if both are slow...

Just one additional note, even though you had the front end on your desktop, were all your other users off of the system? (Even if you have it on your desktop, if SOMEONE has the frontend open on the network drive, it'll slow everyone down) Just checking incase you tried to test it only...

The query method described above will work. If you have a form already that shows the exact data you want, and all you want is to have it filtered you can use the following code: I'm going to assume you are opening the form and want it filtered. Dim strWhere As String 'SQL Syntax for Where...

There are a few ways to do this, depending which you prefer. I tend to alert my users "hey, this file already exists, are you sure you wish to overwrite it?" Dim fs As Object Set fs = CreateObject("Scripting.FileSystemObject") If fs.FileExists(newPath) Then 'Insert code to ask question...

If this is your profession, you're in the wrong profession. If this is an elective, you're in the wrong class. You should have a textbook, or you should be listening in class. Experts aren't here to help you do your school work. Here are some hints for you to find your solution: Look up...

This is where the problem comes in. Your backend is where all the data is stored in the tables, so there should be only one copy of the backend, on the server. Each person who needs to access the data, should have a front end. That frontend needs to be a copy on each person's machine. The...

Just to make sure, is your front end located directly on the local machine? Frontend should be on the local machine (not a shortcut, an actual copy), and the backend on the server. If you're accessing the frontend on the server, with the backend also on the server, this will slow the database...