Computer Learning Zone

In this lesson, we walk through the SQL Server Management Studio interface and cover the essential sections you need to know to get started, especially if you're coming from Microsoft Access. You'll learn about Object Explorer, how to see which server you're connected to, and the main server-level folders like Databases and Security. We focus on creating your first database, explain why SQL Server manages files differently from Access, and clarify important terminology so you'll feel comfortable finding your way around as we get ready to build tables in the next lesson.Full Video: https://599cd.com/SQLSAB01L03

In lesson 2, we will walk through downloading and installing Microsoft SQL Server Express and SQL Server Management Studio (SSMS) step by step, taking the time to explain important options and terminology along the way. I will show you how to choose the right components, set up your local instance, select authentication methods, and connect with SSMS so you have a fully working SQL Server setup ready for future lessons. Video here: https://youtu.be/bG2rj1Q9BOc

I just launched a brand-new course: SQL Server for Microsoft Access Users, and just like my other training, the entire Beginner Level 1 series will be posted FREE on YouTube and my website. Multiple lessons, full Level 1 foundation, NOT a teaser. Lesson 1 is live now and the rest of Beginner 1 will be rolling out soon, so watch the full video now. Lesson 1 is an "explainer" only, so you can also learn plenty from just listening. Enjoy!

Today we discuss some of the most common Microsoft Access questions from viewers, focusing on why tracking monthly payments with one field per month is a classic database mistake and how adding a second related table can solve reporting headaches. We also talk about working with tabbed documents vs. overlapping windows, Power Query merge performance in Excel vs. Access joins, locking fields in edit mode, hiding tables with VBA, the continued relevance of Access in 2026, combo box list caching, report footer formatting issues, and more.

Learn more at 599cd.com/QQ77

I run a Windows machine as a “server” to handle backups and automation, but if I don’t reboot it regularly, Access starts throwing weird errors (like out-of-stack space). Here’s the simple trick I’ve been using: automatically killing Access after my nightly backup a few nights per week so it starts fresh.Learn more at 599cd.com/KillAccess

Every October, the same debate resurfaces here in the US. Columbus Day or Indigenous Peoples Day? It's one of those holidays that means very different things depending on who you ask. Some celebrate exploration and discovery. Others remember conquest and loss. The truth is... both are right.

History isn't clean. It's messy, complicated, and filled with people who did terrible things for reasons that made sense to them at the time. Columbus didn't wake up one morning and decide to be a villain. He was a man of his era, driven by faith, ambition, and the values of a world that saw conquest as divine purpose. Was it brutal? Yes. But so was most of human history.

And it didn't start with Columbus. Conquest and colonization go back as far as we do. The first Homo sapiens leaving Africa displaced or wiped out the Neanderthals. The Romans conquered most of their known world with their coordinated, well-armed legions. The Crusaders spread their faith at the tip of a sword.

Empires rose and fell across every continent long before Columbus, and long after him as well. It's what our species has always done: explore, expand, and, too often, destroy.

But we've also evolved. The same curiosity that sent explorers across oceans, sent humans to the moon, and probes across the solar system. The same human urge to understand "what's out there" has also turned inward, toward understanding who we are, and where we come from. That's real progress.

So maybe the point of this holiday isn't to argue about who deserves a statue. Maybe it's to reflect on what kind of explorers we want to be now. Not conquerors, but learners. Not missionaries, but scientists. Not rulers, but caretakers.

There's a meme that floats around every year: "Celebrate Columbus Day by moving into someone else's house and telling them you live there now." Funny to some people, sure, but it also reminds us how far we've come. We can laugh because we know better.

For more info please visit:

https://599cd.com/ReflectionDay?key=Spotify

Download Microsoft Access for Free? Don't Fall for the Illegal Scams! #msaccess #microsoftaccess https://599cd.com/DownloadAccess?key=Spotify

Today's TechHelp tutorial from Access Learning Zone is all about managing field names when importing data into Microsoft Access from Excel or a text file. I am your instructor, Richard Rost. Often, the field names in imported data can cause issues, such as errors indicating that an item is not found in a collection. Today, we'll discuss how to handle these situations.

A member recently encountered error 3265 while importing a spreadsheet, where Access couldn't find a specific field in the collection despite its apparent presence. After some troubleshooting, it was apparent that a common cause for such issues is incorrect naming conventions in field names. This includes having spaces or non-standard characters in the field names.

In the field's design view, Access usually prevents having trailing spaces in field names. However, if you import data from an external source, such as a spreadsheet, trailing spaces might still accompany field names, leading to errors. Someone else might have originally created the spreadsheet or file, and you might not have the luxury of correcting field names manually.

A brilliant suggestion from one of our contributors was to look for a trailing space after the field name. Indeed, when you import data using Visual Basic for Applications (VBA) and the TransferSpreadsheet method, Access may retain these trailing spaces. This doesn't occur if you import manually via the Access interface, which trims such spaces automatically.

To illustrate, let's say you have a spreadsheet with fields for first name, last name, and phone number. Suppose there's an inadvertent space after the "last name" field. If you import this using VBA, Access keeps the trailing space. When trying to access the field in a VBA recordset, the trailing space causes an error.

To resolve this, you can account for the space within your code by including it in the field name reference. Alternatively, once imported, you can adjust the field names using VBA to remove trailing spaces or correctly match them as needed. This can be achieved by examining the field names and modifying them through VBA programming, which is covered more extensively in my developer classes.

If it's possible to do so, the simplest fix is to modify the original spreadsheet field names before importing. However, when constraints exist, ensure your code accounts for any discrepancies.

A quick note for those following the employee training series: I've recently updated it, and more lessons are on the way. I expected to finish recording the upcoming sessions soon.

I hope this tutorial helps address similar issues you may encounter. For a complete video tutorial with step-by-step instructions on everything discussed here, visit my website. Live long and prosper, my friends.

For more info please visit:

https://599cd.com/ImportedFieldNames?key=Spotify

Today's TechHelp tutorial from Access Learning Zone focuses on tracking employee training and certifications using Microsoft Access. I'm your instructor, Richard Rost, and in response to frequent questions about this topic, I've decided to guide you through creating a comprehensive database system from scratch. This will allow you to effectively monitor which courses employees should take, those they have completed and when, as well as manage the renewal of certifications.

We'll start by designing the necessary tables and then proceed with building the database step by step. This series is at the developer level and will include some VBA programming, although I'll initially focus on constructing the database without it. Forms and tables will be laid out first, and any VBA aspects will be introduced later in the series. For those unfamiliar with VBA, I recommend watching my introductory video, which provides a foundational understanding in about 20 minutes.

Unlike previous tutorials, I'm building this database in real-time alongside you. I have prepared a basic table layout, but we'll be exploring and constructing the database together, learning from any necessary adjustments that arise during development. This hands-on approach mirrors real-world scenarios where feedback and revisions are common.

This comprehensive tutorial series will likely span several parts. As always, I begin my process by outlining the tables and fields required. This is crucial, especially for intricate databases. We'll first look at the department table, necessary for tracking which departments employees and courses belong to. Each department could have multiple roles, leading to a one-to-many relationship.

Our next focus is the course table, which I'll refer to as courseD. This tracks both training courses and certifications, potentially including academic requirements. Categories of courses reflect different departments, such as HR and IT, and may consist of specifics like course codes, descriptions, and resource URLs for further information. The table also logs expiration intervals, important for certification renewals, and whether a course is currently active.

A junction table will link roles to courses, specifying what each position requires. This determines the necessary training for various roles. Additionally, we'll consider course prerequisites where necessary, creating a many-to-many relationship to reflect real-world requirements.

The employee table will connect with other components. Key fields include employee ID, supervisor ID, personal information, and employment dates. A junction table will relate employees to roles, allowing for multiple roles per employee if needed. Details like start and end dates for roles, qualification dates, and whether it's a primary role are tracked here.

Finally, we'll use a junction table to document courses taken by each employee. This will include enrollment dates, deadlines, completion dates, expiration dates, and their status, useful for generating progress reports.

This tutorial covers the initial schema of our database, which we'll refine as needed. Establishing a solid starting framework is crucial, and we'll continue constructing our database in the next session.

For an in-depth tutorial and step-by-step instructions on everything discussed, visit my website. Live long and prosper, my friends.

For more info please visit:

https://599cd.com/EmployeeTraining?key=Spotify

Today's TechHelp tutorial from Access Learning Zone is about automating the import process of data from Excel into Microsoft Access, specifically when dealing with spreadsheets that contain extraneous information. I'm your instructor, Richard Rost. We'll address situations where Excel sheets might have unnecessary rows at the top or bottom, which can complicate the import process.

This topic arises from a question posed by one of our gold members, Brent, who deals with a daily quote report cluttered with unwanted rows above and below the needed data. Currently, he cleans up the file manually before importing it to Access and seeks a way to automate this task.

I've created a sample spreadsheet simulating Brent's issue, involving extra rows at the top with irrelevant data and summary rows at the bottom. Our goal is to import only the necessary data into Access, eliminating all unwanted rows.

Initially, we'll tackle importing this data into Access by discussing how to remove everything above the header row and unnecessary records at the bottom. This process involves setting up a record set and looping through the dataset until we find the genuine header, then erasing any surplus records.

To embark on this task, it's crucial to refer back to previous tutorials on importing Excel sheets into Access, specifically those covering the 'TransferSpreadsheet' command within VBA. You'll need some VBA proficiency, so if you're new to it, watch my introductory video on VBA programming.

As we start, I'll assume the spreadsheet's header contains the phrase "Contact Date." Should this change, you'll need to modify your code. However, such structural changes in reports are infrequent.

We'll systematically process the spreadsheet data using the TechHelp Free Template, downloadable from my site. I'll guide you through setting up an 'Import Excel Data' button to automate the data import process. Using VBA commands like 'DoCmd.TransferSpreadsheet,' we'll import data into a temporary Access table named "ExcelImportT."

Before each import, we should delete the existing temporary table to avoid appending to current data. We'll employ error handling to gracefully manage any missing table scenarios without program interruptions.

Once the data is in Access, we'll loop through the records, purging each until we hit the genuine header row marked by "Contact Date." This operation involves using a record set to pinpoint and remove unnecessary rows both above and below the core data. I'll demonstrate how to build this logic using a basic loop and conditional statements within VBA.

You'll find that automating this process not only saves time but also minimizes human error. While today's tutorial focuses on trimming excess data from the top, tomorrow, we'll continue our discussion on managing data at the spreadsheet's bottom. For those eager to see what's next, remember that members can access subsequent video installments right away.

You can find a complete video tutorial with step-by-step instructions on everything discussed here on my website at the link below. Live long and prosper, my friends.

For more info please visit:

https://599cd.com/ExcelImportCleanup?key=Spotify