Call (323) 285-0939

Microsoft Access Programmer In Flagstaff, AZ

Flagstaff, AZ Microsoft Access Programmer: Access Version Upgrade Support

The Database Was Fine. Then IT Upgraded Office And Half Of It Stopped Working.

An Office update, a move from 32-bit to 64-bit, a Windows upgrade, or a switch to Microsoft 365 -- any of these can break an Access database that has been running without problems for years. Buttons go silent. Reports throw errors nobody has seen before. VBA code that worked fine last Tuesday now flags as broken. The database did not change. The environment around it did.

We update Access databases for Flagstaff businesses so they run correctly on current Office versions -- fixing API declarations, repairing broken references, converting MDB files to ACCDB where that makes sense, and testing the whole file before returning it. When the issue goes deeper than an upgrade, we handle that too. Call (323) 285-0939 and describe what broke.

Get A Rapid Response

MS Access Development For Flagstaff, AZ

Flagstaff sits at 7,000 feet and runs on a mix of healthcare, tourism, university operations, government administration, and long-established local businesses. A lot of those organizations have Access databases that have been in place since the late 1990s or early 2000s. They work -- until an IT department rolls out a 64-bit Office upgrade and the database suddenly does not.

What We Do

Fix Access databases that broke after Office or Windows upgrades, convert MDB files to ACCDB, repair VBA code for 64-bit compatibility, and handle everything else the database needs.

Who We Help

Flagstaff businesses and organizations where an older Access database is part of daily operations and needs to keep running on whatever version of Office IT just deployed.

How We Work

We review the database before touching anything, identify exactly what the upgrade broke, and give you a clear picture of the repair before starting. No surprises on scope.

All work is done remotely. We serve Flagstaff businesses and others across northern Arizona including Prescott, Sedona, Williams, and the broader I-40 corridor.

Talk With Our Principal Programmer

Call: (323) 285-0939

Service Area: Flagstaff, Prescott, Sedona, Williams, And Northern Arizona

Owner And Access Expert: Alison Balter

Microsoft Certified Solutions Developer (MCSD)
Microsoft Certified Professional (MCP)
Microsoft Certified Trainer (MCT)
Microsoft Certified Partner (MCPa)

GET A RAPID RESPONSE

What We Do For Flagstaff Businesses

Flagstaff organizations contact us for a range of reasons. Some have a database that broke after an upgrade. Others are running something that worked for years but has slowly outgrown its original design. The work usually falls into these six areas.

Access Version Upgrade Support

When a 32-bit to 64-bit Office migration breaks VBA code, when an MDB file refuses to open in a newer version of Access, or when buttons go dark after an IT-pushed Windows update -- we find what changed and fix it. That means updating API declarations with PtrSafe, repairing MISSING library references, converting file formats where needed, and testing every form, report, and macro before returning the file.

Custom Access Database Development

New databases built around how a Flagstaff organization actually runs -- intake forms for a healthcare office, booking and billing records for a hospitality business, compliance logs for a government operation, job costing for a contractor. The design starts from the actual workflow, not a template that gets adapted to fit.

Access Database Repair

Broken macros, VBA compile errors, reports throwing wrong totals or blank output, a file that opens but crashes when someone tries to run a specific query. We find what actually broke -- not just the symptom on the surface -- repair it cleanly, and hand back a database the team can trust again without workarounds.

VBA Automation

Weekly reports assembled by hand, monthly data cleanups that take half a day, export routines someone walks through manually every Friday afternoon. We write VBA that handles those jobs automatically, with error handling built in so a bad record does not kill the whole process and leave nobody knowing it failed.

Excel To Access Integration

Spreadsheets that have grown into something harder to manage than the original problem they were solving -- multiple tabs feeding each other, data easy to break, no enforced structure. We move that work into Access where the tables hold the right relationships, the forms control what goes in, and the reports pull numbers without someone assembling them by hand.

Access To SQL Server Migration

When the Access file is being used by more people than it handles well, or when the backup and security requirements have outgrown what a shared file can provide, SQL Server takes over the data side. The Access front end stays in place. Staff keep the screens they already know. The data moves to a more capable back end without a full rebuild.

Practical Database Help For Flagstaff Businesses

Flagstaff is not a typical Arizona market. The elevation, the university, the mix of healthcare and tourism, and a real presence of tribal government administration all shape what businesses there actually need from a database. We see more older files here than in the Phoenix metro -- databases built in the late 1990s that have outlasted two or three IT regimes and a handful of Office versions. They keep running because people work around the parts that stopped working. Then IT pushes a major upgrade and the workarounds stop working too.

Version upgrades are the most disruptive thing that happens to a long-lived Access database. A 32-bit to 64-bit move is the worst of them -- it can silently disable large sections of VBA code without throwing an obvious error, so the database opens and most things appear to work until someone tries to run a specific process and nothing happens. Tracking down every broken API call in a database with ten or fifteen modules takes time, but it is predictable work once you know the file.

Alison Balter is the founder, owner, and principal programmer at MS Access Solutions. She holds four Microsoft certifications: Microsoft Certified Solutions Developer (MCSD), Microsoft Certified Professional (MCP), Microsoft Certified Trainer (MCT), and Microsoft Certified Partner (MCPa) -- one of the first professionals in the industry to earn the MCSD designation. She has authored 15 books on Microsoft Access published by Sams Publishing, including the Mastering Microsoft Access series covering Access 95 through Access 2007. She has produced over 300 internationally marketed computer training videos and is a regular speaker at national Access, SQL Server, and Visual Basic conferences. Her clients have included Shell Oil, Southern California Edison, Accenture, Northrop, the Archdiocese of Los Angeles, Prudential Insurance, the International Cinematographers Guild, and many U.S. government agencies.

Our Arizona Microsoft Access programmer page covers the full scope of our statewide work.

More About Us
Access database repair and development for Flagstaff businesses

How We Work With Flagstaff Businesses

All work is handled remotely -- no scheduling around a drive up I-17, no office visits. The process is the same whether the job is a post-upgrade repair or a new database from scratch.

1

Start With A Conversation

Call or fill out the contact form. We ask what the database does, what changed before the problem started, and what good looks like when the work is done. A Flagstaff healthcare organization called us after their IT department pushed a 64-bit Office upgrade over a weekend. By Monday morning, twelve buttons across four forms did nothing when clicked. That conversation took fifteen minutes and told us exactly what we were dealing with.

2

Review The File

You share the database with us. We go through the VBA code, check the references, look at the API declarations, and map what is broken against what the upgrade changed. For version upgrade work, that means building a complete list of every affected call before writing a single line of replacement code.

3

Do The Work

We update the code, fix the references, and test every form, report, macro, and VBA routine against the target Office version. If we find something else during the work -- a related problem not caused by the upgrade -- we describe it and give you the choice to address it now or note it for later.

4

Return A Working Database

We send back the updated file with notes on what changed and why. For upgrade work, that includes a description of every API fix and every reference that was repaired, so the next person who touches the file understands what was done. We keep records on every file we have worked on, so future changes do not start from scratch.

The Access Work We See From Flagstaff

The work from Flagstaff skews older than what we see from the Phoenix metro. Many of the databases here have been running for fifteen to twenty years, maintained by whoever was available, and never fully documented. The upgrade problem is the most common reason for contact, but it is rarely the only problem once we open the file.

Project Snapshot: Flagstaff Healthcare Organization

Location Flagstaff, AZ Business Type Healthcare organization using an Access database for patient intake, scheduling, and billing records Situation IT pushed a 64-bit Office upgrade over a Friday night. The following Monday, twelve buttons across four forms were unresponsive. The database opened normally and data was accessible, but any button that triggered VBA code did nothing. No error messages appeared. What We Found Nineteen Windows API declarations in three modules used data types incompatible with 64-bit VBA. The affected buttons all called routines that depended on those declarations. Access was silently ignoring the calls rather than running them. There were also four MISSING references from an older ActiveX component the 64-bit install had not carried over. Result All nineteen API declarations updated with PtrSafe and LongPtr where required. Four MISSING references resolved. All twelve buttons restored to full function. Completed in two days. Organization was back to normal operations by Wednesday morning.

Work We Handle For Flagstaff Businesses

  • VBA code updates for 32-bit to 64-bit Office migrations -- API declarations, PtrSafe, LongPtr.
  • Broken reference repair after Office updates, Windows upgrades, or machine migrations.
  • MDB to ACCDB conversion for files that need to run on current Access versions.
  • Repairs on inherited databases where the original developer is no longer reachable.
  • New databases for Flagstaff organizations moving off spreadsheets or paper-based systems.
  • Performance work on older files that have slowed as data has accumulated over many years.
  • SQL Server migration when the file has outgrown what a shared Access back end can handle.

Signs The Database Needs Attention

  • Buttons stopped working after an Office upgrade or a move to a new machine.
  • The database opens but VBA routines do nothing when triggered -- no error, no output.
  • A "Can't find project or library" error appears when the database opens.
  • The file is an MDB and the organization has moved to 64-bit Office 365.
  • Reports that ran correctly for years are now throwing errors or showing wrong data.
  • The database was built by someone who left years ago and the code has never been reviewed.

Why Flagstaff Businesses Work With MS Access Solutions

36+ Years With Access

We have worked with Microsoft Access through every major version change -- from the early releases through the 32-bit to 64-bit transition that has been breaking older databases across Flagstaff organizations. That history means we know exactly what changed between versions and where the problems hide in files that were written before those changes existed.

We Fix The Root Cause

A button that does nothing after an upgrade is a symptom. The cause is a specific API call or a MISSING reference somewhere in the VBA code. We find the actual problem, fix that, and document it -- so the next upgrade does not catch the same file in the same place again.

Remote, No Delays

We use a number of techniques to work with Access database files remotely. No travel, no waiting for someone to drive up from Phoenix. When an upgrade breaks a database that a Flagstaff organization depends on daily, we want to be working on it the same day you call, not scheduling for next week.

Microsoft Credentials And Published Author

Alison Balter holds MCSD, MCP, MCT, and Microsoft Certified Partner credentials -- four certifications few independent Access contractors hold simultaneously. She has authored 15 books on Microsoft Access published by Sams Publishing and produced over 300 internationally marketed computer training videos. Her books are used as desk references by development teams at major corporations.

What Clients Say

MS Access Solutions client Mary Forman, Country Natural Beef

Mary Forman

Country Natural Beef

Alison Balter has been my SQL/Access programmer for 5 years now! She did a major overhaul/face lift to an Access system that was 'built' in the early '90s, had an upgrade for the Y2K nonevent and morphed through several techs over the years. Needless to say, we became good friends as we spent many a late hour pondering, planning and implementing. She was willing to work around my 'work day' so we had access to Access. My experience is that programming work almost always takes longer than expected. Alison is good at budgeting time and keeping on schedule and on task. She has always been willing to 'teach' as well as 'do' so that I have a feel for the bigger picture and can be somewhat self-sufficient on a day to day basis. She has helped me design safeguards to the programs so that inadvertent errors do not occur. I am honored to know Alison and pleased to recommend her as a SQL/Access guru!

Read more client reviews

Tech Talk: Access Topics Flagstaff Businesses Ask About

Two version-compatibility topics that come up regularly when fixing Access databases for Flagstaff organizations.

Why 64-Bit Office Breaks VBA Code That Ran For Years

Most long-lived Access databases contain at least a few Windows API calls -- Declare statements in VBA that reach directly into Windows system libraries to do things Access cannot do on its own. Common examples are file dialog boxes, registry reads, system date and time functions, and anything that interacts with the Windows shell. These declarations were written for 32-bit Office and they work without changes for as long as the database runs on a 32-bit install.

The 64-bit runtime handles memory addresses differently. Pointers -- the values that tell the code where data lives in memory -- are 64 bits wide instead of 32. A Declare statement written for 32-bit VBA uses Long as the data type for pointer values, which is a 32-bit integer. In 64-bit VBA, using Long as a pointer type is not just wrong -- it is potentially dangerous, so Access refuses to run any module that contains outdated declarations. The entire module goes dark. Every procedure inside it stops responding. No error message appears. The code is simply not executed.

The fix requires two things. First, every Declare statement needs the PtrSafe keyword added immediately after Declare. This tells the 64-bit compiler that the declaration has been reviewed and is safe to run. Second, any Long variable used as a pointer needs to be changed to LongPtr, which is a conditional type that resolves to 32 bits on a 32-bit install and 64 bits on a 64-bit install. A database updated this way will run correctly on both 32-bit and 64-bit Office without needing separate versions of the file.

The practical challenge is finding every affected declaration. A database with fifteen or twenty modules can have API calls scattered across many of them, and some calls are in standard modules while others are in class modules or form code sections. The audit has to be thorough. Missing one is the same as missing all of them -- the module containing the overlooked declaration will still fail to run.

MISSING References -- Why They Happen And How To Clear Them

When a VBA project references an external library -- a type library, an ActiveX control, a COM component -- Access records the path to that library in the project's reference list. If the library moves, gets updated to a version with a different registration, or simply does not exist on a new machine, Access marks the reference as MISSING. Any code that depends on types or functions from that library stops compiling.

The symptom is usually a "Can't find project or library" error at startup, or code that compiled fine on one machine but throws errors immediately on another. Office upgrades are the most common trigger, particularly moves from older Office versions to Microsoft 365, where several library versions changed and some older controls were dropped entirely.

Clearing a MISSING reference is straightfoward: open the VBA editor, go to Tools then References, find the entry marked MISSING, uncheck it, then scroll through the available libraries to find the current version of the same component and check that instead. The complication comes when the old library no longer exists in any form -- retired ActiveX controls, for example -- and the code that used it needs to be rewritten to use a supported alternative. That is less common but not rare in databases that have been running since the early 2000s.

One note worth flagging: a database can have multiple MISSING references simultaneously, and fixing one will not automatically surface the others. After resolving the first MISSING entry, recompile the project and check the reference list again. In a database with four MISSING references, it takes four separate fix-and-recompile cycles to get to a clean compile state.

Frequently Asked Questions

Question: Our Access Database Stopped Working After IT Upgraded Office To 64-Bit. Half The Buttons Do Nothing Now. What Happened?

Answer: The 32-to-64-bit switch breaks any VBA code that calls Windows API functions directly. Those declarations use data types that do not exist the same way in 64-bit, so Access silently disables the code rather than running it incorrectly. The fix is to update the Declare statements with the PtrSafe keyword and replace any Long types used as pointers with LongPtr. How much work that is depends on how many API calls are in the database -- some files have one or two, others have dozens spread across multiple modules.

Question: We Get A "Can't Find Project Or Library" Error Every Time We Open The Database. What Does That Mean?

Answer: A library the VBA project depends on is no longer where Access expects it. This usually happens after an Office update, a Windows update, or a move to a different machine. Open the VBA editor, go to Tools then References, and look for any entry marked MISSING. Uncheck it, find the current version of the same library, and check that instead. If you are not sure which library is the right replacement, we can walk through the file and identify it.

Question: We Have An Old MDB File That Has Been Running Since The Early 2000s. Is It Worth Converting It To ACCDB?

Answer: It depends on what is driving the question. MDB format has real limits -- a stricter security model Microsoft no longer supports, no multi-valued fields, and it cannot take advantage of performance improvements in newer Access versions. If the file is running without problems, conversion is not urgent. If Office upgrades are breaking it regularly or IT is moving to 365 on 64-bit installs, then converting as part of a broader cleanup makes sense rather than patching it each time a new update lands.

  • Back up the original MDB before touching anything
  • Open in current Access and convert to ACCDB
  • Retest every form, report, query, and macro
  • Fix any VBA references that broke during conversion
  • Update any external links that pointed to the old file path

Question: Our Reports Were Printing Fine Last Year. Now Columns Overlap And The Totals Are Cut Off. Nothing Changed On Our End.

Answer: Something did change -- most likely the default printer or its driver. Access ties report layout to the printer that was active when the report was designed. When the default printer changes, the margins, column widths, and page breaks all recalculate against the new driver and the layout shifts. The cleanest fix is to export the report to PDF using the OutputTo VBA method with acFormatPDF, which bypasses the printer driver entirely and produces consistent output regardless of what is set as the default.

Question: Do You Work With Flagstaff Businesses Remotely?

Answer: All of our work is done remotely. We use a number of techniques to work with Access database files remotely. No travel, no scheduling around a drive up I-17. Most of what we do for Flagstaff clients is handled within a few business days, and larger projects get a clear timeline before we start.

Question: We Have Been Tracking Inventory In An Excel Spreadsheet For Five Years And It Is Getting Hard To Manage. Would Access Be A Better Fit?

Answer: Almost certainly, yes. Spreadsheets work well for analysis but not for tracking over time. Once you have more than a few hundred rows, multiple people editing the same file, or any need to connect inventory to purchase orders or job records, the spreadsheet creates more work than it saves. Access handles structured data, enforces relationships between tables, and produces reports without manual cross-referencing. We would look at how the spreadsheet is set up and build the Access database around the actual workflow rather than a generic layout.

Question: What Kinds Of Flagstaff Businesses Do You Typically Work With?

Answer: Flagstaff has a mix of healthcare operations, hospitality and tourism businesses, university-adjacent organizations, contractors, tribal government administration, and small manufacturers. The Access work there tends to reflect that variety -- databases tracking patient intake, booking and billing records, compliance logs, job costing, and inventory for businesses serving both locals and seasonal visitors.

The situations we see most often involve older databases that have not been touched since the original developer left, files breaking on 64-bit installs, and organizations that have outgrown what the original database design was built for. If the database is part of how your Flagstaff operation runs, we can help with whatever it is doing that it should not.

Related Services

Flagstaff is one part of a broader set of Access database work we do across Arizona. These service pages cover the specific types of work that come up most often statewide.

Custom Access Database Development

New Access databases built from scratch around how your Arizona business works, when there is no existing database to start from or the current one needs more than repair.

Excel To Access Data Integration

Move data work out of spreadsheets and into Access where the structure holds and reporting does not require manual cleanup every time someone asks for a number.

Automation With VBA

Write the code behind imports, exports, buttons, and repeatable routines that people are still handling step by step every day.

Database Optimization And Performance Tuning

Speed up slow forms, queries, and reports in Access databases that have grown over the years and are no longer running the way they did when first built.

Access To SQL Server Migration

Move data into SQL Server when the Access file needs a back end that handles more users, more data, and better backup and security options.

Maintenance, Repair, And Support

Fix broken buttons, references, macros, and older Access systems still running operations that depend on them every day.

More Arizona Cities We Serve

Flagstaff is one market in a longer list of Arizona cities where we handle Access database work. These pages cover how we approach similar problems across the state.

Google map image for Phoenix, Arizona

Phoenix Access Programmer

Phoenix brings the highest volume of Access work across the state -- large files, complex repair, and databases that have been accumulating problems across multiple IT regimes.

Learn More
Google map image for Tucson, Arizona

Tucson Access Programmer

Tucson work tends toward cleanup and targeted repair -- older files that have drifted enough to cause friction but still have solid underlying data worth preserving.

Learn More
Google map image for Mesa, Arizona

Mesa Access Programmer

Mesa requests lean toward day-to-day fixes and form cleanup -- the kind of recurring issues that add up quietly until someone decides to deal with them properly.

Learn More
Google map image for Chandler, Arizona

Chandler Access Programmer

Chandler often involves split database work -- separating front and back ends and resolving the locking issues that follow when a shared file outgrows its original setup.

Learn More
Google map image for Gilbert, Arizona

Gilbert Access Programmer

Gilbert work leans toward automation -- replacing manual imports, exports, and recurring jobs with VBA that runs without someone managing each step.

Learn More
Google map image for Glendale, Arizona

Glendale Access Programmer

Glendale work centers on incremental improvement -- keeping what already runs and fixing what does not, without rebuilding more than the situation calls for.

Learn More
Google map image for Scottsdale, Arizona

Scottsdale Access Programmer

Scottsdale projects tend to grow once the file is open -- a specific fix leads to uncovering a broader structural issue that has been building for a while.

Learn More
Google map image for Peoria, Arizona

Peoria Access Programmer

Peoria databases often carry unfinished automation -- macros that mostly work and manual steps that someone still walks through every morning when they should not have to.

Learn More
Google map image for Tempe, Arizona

Tempe Access Programmer

Tempe work tends to start with a specific repair and expand into documentation -- understanding what the file actually does before any changes are made.

Learn More
Google map image for Surprise, Arizona

Surprise Access Programmer

Surprise databases are usually inherited -- the challenge is mapping what exists accurately enough to change something without quietly breaking something else.

Learn More
Google map image for Avondale, Arizona

Avondale Access Programmer

Avondale work tends to center on multi-user locking -- databases that were built for small teams and now need a proper split and conflict handling to keep running reliably.

Learn More
Google map image for Buckeye, Arizona

Buckeye Access Programmer

Buckeye is where import and export automation comes up most -- vendor feeds, receiving logs, and weekly data routines that need to run without someone babysitting them.

Learn More
Google map image for San Tan Valley, Arizona

San Tan Valley Access Programmer

San Tan Valley databases have often grown faster than planned -- the work is catching the design up to the size and complexity the business has reached.

Learn More
Google map image for Yuma, Arizona

Yuma Access Programmer

Yuma operations run on tight schedules -- agriculture, logistics, and compliance reporting where a broken database routine cannot wait for a convenient repair window.

Learn More
Google map image for Goodyear, Arizona

Goodyear Access Programmer

Goodyear work is usually practical and focused -- specific repairs and cleanup that get the database back to a state the team can trust day to day.

Learn More

Useful Microsoft Resources

Ready To Talk About Your Flagstaff Access Database?

Call (323) 285-0939 or use our Contact Us form. We review the database, identify what the upgrade or repair involves, and give you a clear picture before anything starts. For a broader look at our Arizona work, visit our Arizona Access programmer page.

Alison Balter is the founder, owner, and principal programmer of MS Access Solutions. She holds four Microsoft certifications: Microsoft Certified Solutions Developer (MCSD), Microsoft Certified Professional (MCP), Microsoft Certified Trainer (MCT), and Microsoft Certified Partner -- one of the first professionals in the industry to earn the MCSD designation.

Alison is the author of 15 books on Microsoft Access published by Sams Publishing, including Alison Balter's Mastering Access 95 Development, Mastering Access 97 Development, Mastering Microsoft Access 2000 Development, Mastering Microsoft Access 2002 Desktop Development, Mastering Microsoft Access 2002 Enterprise Development, Mastering Microsoft Office Access 2003, and Mastering Microsoft Office Access 2007 Development, among others. She has also produced over 300 internationally marketed computer training videos and is a regular speaker at national Access, SQL Server, and Visual Basic conferences. She was a featured speaker on the Visual Basic 4 and Visual Basic 5 World Tours, sponsored by Microsoft.

Her clients have included Shell Oil, Southern California Edison, Accenture, Northrop, the Archdiocese of Los Angeles, Prudential Insurance, the International Cinematographers Guild, and many government agencies. She has been a contributing columnist for Access/Office/VB Advisor and served as past president of the Independent Computer Consultants Association of Los Angeles.

MS Access Solutions Flagstaff, Arizona Service Area Map

Call (323) 285-0939 or use our contact form to talk through your Flagstaff Access database project.