DMS Systems, Data, Security, I.T.

Dealers discussing the transition from ADP Web Suite to ADP Drive Express report significant performance concerns, with multiple users noting the cloud-based Drive system is noticeably slower than the on-premise Web Suite, likely due to the server relocation from local dealerships to a centralized Michigan data center. While one user acknowledges Drive offers improved user interface design, the speed disadvantage is severe enough that at least one dealership fears it could disrupt daily operations. The consensus suggests careful consideration before migrating, particularly for high-volume dealerships dependent on system responsiveness.

Reynolds and Reynolds announced plans to eliminate inbound modem access for third-party vendors effective January 4, 2010, forcing dealers to find alternative data access methods during the holiday period. The thread discusses confusion around whether the requirement was mandatory or voluntary, with recommended solutions including client-side applications installed on dealership LANs (like DMI and SelectQu), Reynolds' own RCI interface, or the company's RPM Remote Client Access. The key insight is that vendors needed to migrate from modem-based access to network-based solutions or official Reynolds APIs to maintain service continuity.

GreggTompkins seeks guidance on extracting service and parts data from multiple dealership locations using DMS tools, specifically asking which databases to query and whether security restrictions will impede the process. CliffC provides technical recommendations (Query Builder, AA.SER.WIP for service, PROD.HIST and PRH.YYMM for parts) and advises that automation will be problematic, recommending instead that GreggTompkins cultivate a relationship with someone who has access to system 6210 for future needs. The thread suggests that while data extraction is possible, manual processes and internal relationships may be more practical than automated solutions given system restrictions.

A dealer asks whether Intellipath coupon criteria can be modified locally or must go through Reynolds and Reynolds for every change, noting that their current setup prints identical coupons regardless of customer or service type. A Reynolds and Reynolds VP responds by offering direct assistance from an Intellipath specialist to discuss the dealer's customization goals and available solutions. The thread suggests that local customization options may exist, though no technical details are provided before resolution is offered.

Dealers using ERA 20.0 report significant problems following a forced server-side upgrade, including corrupted i-descriptors and broken custom 6910 processes, with minimal visible improvements beyond a scrolling feature that users find trivial. The thread reveals frustration that Reynolds & Reynolds appears to have inadequately tested the upgrade and poorly addressed resulting damage, with one user noting their dealer group suffered notable disruption. A potential patch version (20.05) is rumored to be in testing, suggesting Reynolds may be working to address the issues, though users remain skeptical about the overall value of the upgrade.

A dealer seeks help adding an email field from Reynolds record 4770 to a custom form in record 4816 using Reynolds Form Programming, a BASIC-like coding language that most dealers no longer have access to. After community members confirm that form editing access is limited and requires special permissions, the original poster successfully contacts Reynolds support and discovers the solution is straightforward—just three lines of code to print the email address field at the desired screen coordinates. The thread concludes with the poster sharing the exact code modification needed, establishing themselves as a resource for other dealers facing similar form customization challenges.

Dealers are frustrated with Reynolds' Contact Management system for failing to automatically remove bad email addresses from their database after bounces, a standard feature in competing CRMs. The thread reveals a broader pattern of complaints about Reynolds' product design and customer service—including inability to segment past customers from recent buyers in campaigns, slow license provisioning, and poor tracking capabilities for external marketing materials—with multiple users expressing that these gaps stem from fundamental platform limitations rather than simple oversights.

Dealers express frustration with Reynolds and Company's technical decisions, particularly the forced migration from the legacy ERALink system to ERAccess, with the original poster criticizing the "security" justification as a cop-out. The thread reveals broader concerns about Reynolds' strategic direction, including unconfirmed rumors of cost-cutting (focusing on ~2,500 large clients), potential acquisition by DealerTrack, and leadership changes following market share decline. The consensus emerging from multiple experienced dealers is that Reynolds' dominance will eventually erode as new dealership decision-makers seek better-managed vendor relationships and improved alternatives become available.

Jarrett shares information about OpenTrack, DealerTrack DMS's API program for real-time data exchange, positioning it as an affordable alternative to Reynolds & Reynolds' RCI program that prioritizes secure data sharing over revenue generation. The thread appears to discuss technical implementation details and benefits for dealers who have migrated from ERA to DealerTrack DMS. A vendor (Jeff Kershner) confirms the value of this information for the community.

An advertising company seeks pricing information for Reynolds RCI (data integration) access, but Reynolds requires extensive paperwork before disclosing costs. Respondents indicate that RCI certification is expensive (estimated $70K+ as of 2007), time-consuming to obtain (6+ months in queue), and subject to NDAs that prevent vendors from sharing specifics—making it impractical for dealers with fewer than 100 locations. The thread offers an alternative solution by directing interested parties to third-party companies that provide authorized DMS data pulls without the RCI certification burden.

A dealer using Reynolds DMS reports an issue with Line 4 (Model Description) in used car listings, where redundant terms like "4DR" and "SDN" cannot be removed or replaced with important features like "NAV" to accurately reflect the vehicle's selling points. After discussion with Jeff Kershner, the user learned they could edit the trim in HomeNet, which would update the next day, or use import conversions to customize inaccurate DMS data. The thread concludes with the user successfully making changes but expressing a wish for Reynolds to allow direct custom edits to Line 4.

A dealer seeking to extract financial data from Reynold & Reynolds DMS systems across multiple dealerships asks for vendor recommendations, mentioning that RCI certification is typically required. The thread generates responses from two primary vendors—SelectQu (Division of Dominion Dealer Solutions) and StoneEagle Group—both offering data polling services, with an independent user endorsing SelectQu's flexibility and execution. The key insight is that for large-scale DMS data extraction, engaging a certified third-party vendor is the practical path, with SelectQu and StoneEagle emerging as the most recommended options in this community.

A dealer frustrated with RPG's limitations for creating reports in the ADP DRIVE system seeks alternative solutions; the community confirms RPG is the standard tool but recommends learning its more advanced "English" syntax for better functionality, and suggests exploring third-party resources like DealersEdge forums and Power Programs for additional reporting flexibility. The key insight is that while ADP's reporting capabilities may feel restrictive compared to legacy systems, workarounds exist through English statements and third-party programming tools that ADP allows.

A new industry professional shares his frustration after failing to reach Dealertracks sales for a week following an initial inquiry, raising concerns about their responsiveness and capacity. Other forum members provide context that Dealertracks and competitors are experiencing unusually high demand due to industry migrations, though one notes this doesn't typically excuse poor communication. The thread concludes positively when Dealertracks identifies and fixes an internal routing error in their lead process, ultimately scheduling a demo for the original poster.

Automotive dealers using Reynolds and Reynolds ERA DMS software discuss methods for extracting and analyzing data through Query Builder, sharing practical workarounds for common challenges like field wrapping issues when exporting to Excel. Key solutions mentioned include disabling word-wrap in the report wizard, outputting to .dbf files for better data management, and selectively pulling relevant fields from core files like serindex and fimast rather than attempting to extract all fields at once. The thread reveals that while ERA's query interface is considered clunky by many users, experienced professionals have developed efficient workflows to automate reporting and data analysis across sales, service, parts, and accounting departments.

Dealers express frustration with Reynolds and Company's DMS system over data ownership restrictions, vendor lock-in through their RCI platform, and perceived security measures that actually serve to consolidate control rather than protect dealers. Posters argue that Reynolds exploits dealers due to lack of industry-wide pushback and absence of viable modern alternatives, with one commenter noting the irony that dealers cannot use their own data contained in systems they own. The underlying consensus is that only significant contract non-renewals or regulatory intervention (like NADA involvement) will force Reynolds to change exploitative practices.

A dealer IT professional reported that installing ERAccess software crashed three computers running Windows XP Embedded operating systems with fatal boot errors, while installation succeeded on standard Windows systems. The community offered troubleshooting suggestions (safe mode, recovery console, minidump analysis), but the original poster ultimately resolved the issue by reloading the OS on affected machines rather than reinstalling ERAccess, suggesting the software has compatibility problems with certain platforms that vendor R&R was unwilling to address.

A new forum member asks whether UCS and R&R dealership systems are the same following a merger, and seeks guidance on remote access to the UCS DMS. Responses clarify that the systems remain distinct—UCS uses "Power" software while Reynolds & Reynolds uses "ERA"—and that choosing the right remote access tool depends on specific business needs. The thread provides initial clarification but appears incomplete, with the final reply cut off before delivering full guidance on implementation.

Multiple DMS administrators reported widespread Query Builder errors across Reynolds/ERALink systems starting yesterday, with affected dealerships unable to export sales and service data despite having proper account permissions. Investigation revealed that Reynolds had intentionally disabled certain files and Query Builder functionality as a security measure, requiring developer tickets to restore access—a change that affected 6-10+ dealerships across multiple clients. The thread evolved into frustration with Reynolds' broader practice of progressively restricting data access features to force customers into purchasing additional products or services.

Alex Snyder shared a humorous YouTube video of ADP employees performing a cheesy promotional song/dance ("We are ADP!"), which sparked playful banter among forum members about the dated nature of the production style and 1980s aesthetic. The thread is lighthearted commentary poking fun at corporate promotional videos, with Ryan Leslie comparing it unfavorably to other aging pop culture references before Alex good-naturedly called him out for the unsolicited criticism.

A dealer asks about RAXconsole, a software that Reynolds TAC wants to install on ERA servers. According to a respondent with inside knowledge, RAXconsole is Reynolds' proprietary Windows executable designed to replace the legacy terminal emulation software (ERALink/Wintegrate) with a modern GUI interface, and it functions as an update/patch system that enables the SDC server to create a reverse proxy connection to Reynolds' update servers. The thread provides clarification on this transitional technology but lacks extensive community input or debate.

A dealer using R&R Contact Management struggles with implementing a separate Internet Lead Management (ILM) tool while remaining locked into a two-year CM contract, concerned about system integration issues. The discussion evolves into a broader debate about dealership culture, revealing that floor sales staff resistance to CRM adoption and collaboration with internet departments stems primarily from compensation structures that incentivize competition rather than teamwork. The key insight is that pay plans—not training or technology—drive behavior, and dealership leadership must align compensation with collaboration goals to resolve inter-departmental conflict.