Last Update: 2024 - 05 - 21
Conversion New — Audi A3 8v Facelift
by Philipp Stiefel, originally published April 22 2020, last updated April 22 2020
Quite often one of the major problems with the migration to the 64bit-Edition of Microsoft Access is the Microsoft TreeView Control included in the Microsoft Windows Common Controls library. For a very long time this control was not available for 64bit.
This text is written with the TreeView control in close focus. But all the information here also applies to the other Common Controls, like the ListView, ImageList, and ImageCombo.
Prologue – (Un)Availability of the 64bit TreeView
In the early days of 64bit Office/Access there was increased confusion about this topic because apparently Microsoft included the Common Controls in the 64bit installation, but that were the 32bit Common Controls, which did not work in 64bit applications.
After years of countless support request and complaints, Microsoft finally decided to release a 64bit edition of the Microsoft Common Controls particularly for the use with Microsoft Office. This was released in the Update 1707 of July 27 2017 (Build 8326.2058).
Quote of the relevant info:
Office suite: Non-security updates
Add 64-bit support for mscomctl.ocx, allowing users working in 64-bit versions of Office to create, edit, and open macro files containing the Common Controls.
As there still is ongoing confusion on how to install and use the 64bit Edition of the Microsoft Common Controls, I decided to investigate the issues and write down my findings.
No 64bit TreeView with Access 2013 (and 2010)
I started my investigation with an installation of Microsoft Access 2013 64bit in Windows 8.1 (64bit). I’m very certain that the operating system is not relevant in this context and it will not matter whether this is done on Windows 7, 8 or 10.
With a default installation of Microsoft Access 2013 64bit there is neither a MSCOMCTL.OCX file in C:\WINDOWS\SysWOW64\ (this is the system directory of the 32bit subsystem!) nor in C:\Windows\System32 (the default 64bit system directory). If I try to insert an ActiveX Control into an Access form there is no Microsoft TreeView Control available in the list of installed ActiveX Controls.
The 64bit TreeView with Access 365 (and 2019)
Then I installed the 64bit Edition of Microsoft 365 Click-to-Run (C2R). At the time of writing, I got the Version 2003 of Access 2016/365. Installing this did not make any difference regarding the MSCOMCTL.OCX file in the Windows system directories mentioned above.
We must be aware of the fact that the C2R-Editions of Office are installed into a semi-virtualized environment (sandbox). For a 64bit Office installation, all files that are not immediately a part of Office will not be installed in the usual, global system directories but in the directory C:\Program Files\Microsoft Office\root\vfs (vfs = Virtual File System). The System subdirectory in the above directory now contains our desperately needed MSCOMCTL.OCX file.
After starting my newly installed Access 2016 and creating a new form, I’m immediately able to insert a TreeView Control into this form. The TreeView visually appears “normal”, displays the sample nodes and a small bit of test code I created, works also as expected, including the event handling.
Conversion New — Audi A3 8v Facelift
Warning: You cannot simply swap a bumper. The interfaces are different.
To do a complete and professional conversion, you need these components:
A common point of confusion in the market is the difference between an A3 conversion and an S3 conversion.
If you own a standard A3 and want to convert it to the facelift look, you can choose between standard A3 facelift parts or the more aggressive S3 facelift parts (which feature larger side air intakes and specific grille badging). While the S3 bumper fits, it often requires specific S3 crash bars and fog light delete covers, adding another layer of complexity to the parts hunt.
Problem: Swapping the steering wheel triggers the airbag light. Solution: If you keep the old airbag, the new wheel may not fit. Buy a FL airbag. Clear the code with VCDS.
Do not buy a junkyard front bumper and expect it to fit. Here is the full inventory for a complete conversion.
Problem: After swapping the MMI or Virtual Cockpit, the screen shows "Component Protection Active." Solution: Only an Audi dealer or a specialized tuner with online ODIS access can remove this. It costs roughly $150-$250.
Yes, but with caveats.
Before sourcing parts, you must understand what changes. The 8V facelift is not a simple bumper swap; it involves a complete optical redesign.
Conclusion
The Audi A3 8V facelift conversion is a substantial project that can breathe new life into an older vehicle. While it can be a complex and potentially costly process, the end result can be highly rewarding, offering the updated look and feel of the later facelifted model. Whether you're looking to improve the car's aesthetics, update its technology, or simply want a change, a facelift conversion can be a great option for A3 8V owners. However, it's essential to consider the feasibility of the project, given your skills, budget, and the car's condition. With careful planning and execution, an Audi A3 8V facelift conversion can be a successful and satisfying endeavor. audi a3 8v facelift conversion new
Converting a pre-facelift Audi A3 8V (2013–2016) to the "8V.5" facelift style (2017–2020) is a popular but technical modification that involves swapping key body panels, lighting, and interior technology. While simple upgrades like the grille are DIY-friendly, a full conversion requires significant structural and electrical work. Essential Conversion Parts List
To achieve a full factory-like facelift, you generally need the following components from the 2017+ model year:
The Audi A3 (8V) facelift conversion! That's a great project. Here are some helpful features to consider:
Exterior Features:
Interior Features:
Performance and Handling:
Other Features:
Conversion Considerations:
If you're planning to convert your Audi A3 (8V) to a facelift model, consider the following:
Keep in mind that a conversion like this may require significant investments of time, money, and expertise. Make sure to research thoroughly and plan carefully before embarking on this project. Warning: You cannot simply swap a bumper
Title: The Definitive Guide to the Audi A3 8V Facelift Conversion: Modernizing the Modern Classic
Introduction
The Audi A3 8V platform, produced roughly between 2012 and 2020, represents a pivotal era for the compact luxury sedan and hatchback. However, in 2016, Audi released a significant "Facelift" (LCI) update that drastically modernized the car’s aesthetics, most notably through the introduction of Matrix LED headlights and a sharper grille design.
For owners of the "Pre-Facelift" (2012–2016) models, the visual difference between their car and the newer 2017+ models is striking. Consequently, the "Facelift Conversion"—retrofitting newer body parts onto older cars—has become one of the most popular modifications in the Audi community. This paper outlines the scope, components, technical challenges, and considerations involved in performing a successful Audi A3 8V facelift conversion.
I. Visual Motivations: Pre-Facelift vs. Facelift
Understanding the motivation for this conversion requires comparing the two generations.
II. Core Components of the Conversion
A full facelift conversion is not a single-part swap; it is a systemic overhaul of the vehicle’s front and rear aesthetics.
1. Front End Conversion This is the most complex aspect of the project. It typically requires:
2. Rear End Conversion
III. Technical Challenges and Electronics
The mechanical bolting of parts is labor-intensive but straightforward for a skilled body shop. The true complexity lies in the electronics.
1. Headlight Coding Facelift headlights operate on different software protocols than Pre-Facelift cars. Simply plugging them in will result in flickering, error codes on the dashboard, or non-functional high beams.
2. Taillight Wiring Similar to the front, the rear lights require wiring modifications. The Pre-Facelift wiring loom does not match the Facelift pinout. This requires either cutting and splicing wires (not recommended) or purchasing a dedicated conversion wiring loom.
3. Dynamic Indicators A desirable feature of the Facelift is the "dynamic" sweeping turn signal. Achieving this function on a Pre-Facelift car is difficult. It often requires replacing the door control modules and heavy re-coding, as the car's internal architecture was not designed for that specific animation. Many conversions settle for static (non-sweeping) indicators, which are still an aesthetic upgrade.
IV. Parts Acquisition and Costs
The cost of a conversion varies wildly based on the route taken: New OEM parts vs. Used parts.
V. Legal and Resale Considerations
VI. Conclusion
The Audi A3 8V Facelift conversion is a rewarding project that can extend the visual lifespan of an older vehicle, bringing it visually up to date with current market standards. However, it is not a simple bolt-on affair. It requires a deep understanding of automotive bodywork, specialized knowledge of VAG electronics, and a significant financial investment. Do not buy a junkyard front bumper and expect it to fit
For the dedicated enthusiast, the result—a refreshed, modern Audi with superior lighting and aggressive styling—justifies the effort. For the casual owner, the technical hurdles may outweigh the aesthetic benefits. Proper planning, sourcing quality OEM parts, and utilizing experienced specialists are the keys to a successful conversion.
Redistribution to Access 2013, 2010 and early version of Access 2016
If I try the same in old Access 2013 installation, I still cannot insert the TreeView controls, as it is still missing from the list of ActiveX Controls. Opening the database, I created with Access 2016 earlier, and then opening the form with the TreeView resulted in in the error “There is no object in this control.”. – I was expecting this due to the Office 2016 sandbox.
The logical next step would be to copy the OCX file to the global System32 directory and register it there.
So, I copied the MSCOMCTL.OCX file from the Office virtual files system into the C:\Windows\System32 folder. I then ran cmd.exe as Administrator and executed
Unfortunately, this failed with the error message “… the call to DllRegisterServer failed with error code 0x8004005.” – Well, this might have happened because there are some dependencies of MSComCtl.ocx that in the Office-VFS\System folder, which I did not copy.
Next, I tried to copy all the files from Office-VFS\System to a new folder and run regsvr32 for the OCX in that folder. – No luck, the error message quoted above persisted.
I’ve got no clue what the problem is here. Maybe I missed a step. If you see my mistake, please let me know!
Hacking the Redistribution
The normal and recommended way to register a DLL or OCX on any system is to use regsvr32.exe as I tried above. However, in the end for most ActiveX/COM controls and components it boils down to adding some keys and values to the Windows Registry.
As a workaround to the dead-end with using regsvr32 to register the OCX, I started RegEdit and looked for the relevant Registry keys and values for the TreeView Control of my Office 365 C2R installation.
These are usually in the HKEY_CLASSES_ROOT branch of the Registry and are below the class name (“MSComctlLib.TreeCtrl”) and the class id (=CLSID) (“C74190B6-8589-11D1-B16A-00C0F0283628”) of the control or component. As the C2R-Office is in a sandbox these values are also not in their usual registry path but sandboxed below the path HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\ClickToRun\REGISTRY.
I then exported these two keys with all their subkeys to.reg text files. I then edited those files and replaced their registry path with the usual base path HKEY_CLASSES_ROOT. After that I merged the edited files with the registry again.
(Reminder: I previously copied the MSCOMCTL.OCX file to C:\Windows\System32\. This is the file these re-imported registry values are pointing to!)
Et voilà! After merging my edited files in the registry, the Microsoft TreeView Control shows up in the list of insertable ActiveX controls in Access 2013! I also quickly tested my small code fragment from above and it worked!
You can download the reg-script I used to add the registry settings for Access 2013. However, this is intended as an example only. You should not use it to register the TreeView on your computer. Rather export these registry settings from your own installation, to make sure you get the settings matching your version of the TreeView control.
32bit/64bit compatibility?
What if we need to use one and the same database application file in Access 32bit as well as Access 64bit? – If is an accdb (not compiled to accde) you can usually work with one and the same file without a problem. (If you use the Windows API, you need to make sure your API declarations are 64bit compatible.)
What about the TreeView in this situation? If I create a form with a TreeView in Access 2016 64bit where the TreeView control is automatically available, I can open the very same database file with Access 32bit (tried Access 2016/365, Access 2013, and Access 2010) and it works right away.
However, if I try a form with a TreeView control that was created in Access 2013 after applying the above registry hack, I get an error message in Access 32bit (again: Access 2016/365, Access 2013, and Access 2010).
“The expression [AnyEvent] you entered as the event property setting produced the following error: There was an error loading an ActiveX control on one of your forms or reports.”
This usually indicates a problem with binary compatibility between different versions of a control. However, this cannot be the case here, otherwise it should not have worked with the Access-2016-created file.
I guess, I must have missed something in my redistribution hack above. – I’m not really affected by this problem, so I’m not investing more time into fixing this problem. But, again, please let me know if you know the solution to the issue.
The other way round, creating a form with TreeView control in Access 32bit and then using this form in Access 64bit worked without any problems in the default Access 2016/365 installation as well as in Access 2013 with the “hacked” TreeView installation.
Conclusion
Current versions of Access 2016/365 (and probably Access 2019 as well) have a fully compatible MsComCtl TreeView control, which works out of the box.
However, this control is not intended for redistribution on its own, neither technically nor legally. If you need to use it with an older version of Access, you can probably work around the technical limitations using an approach like mine. But this does not solve any potential legal issues. - I’m not aware of any redistribution license for the 64bit MsComCtl.ocx.
If you want to distribute an application using the MsTreeView to users which don’t have an Access version with the 64bit-TreeView, the best option is probably using the Access 365 Runtime, which is receiving updates and thus should also include the 64bit common controls. – Disclaimer: I have not tested the Access 365 Runtime yet.
I will never share your email with anyone. You can unsubscribe any time.
This email list is hosted at Mailchimp in the United States. See our privacy policy for further details.
© 1999 - 2024 by Philipp Stiefel - Privacy Policiy