Search found 123 matches
- Wed Jul 02, 2025 6:36 am
- Forum: Xbase++ 2.0
- Topic: ADS sp_mgGetLockOwner PROCEDURE
- Replies: 2
- Views: 428
Re: ADS sp_mgGetLockOwner PROCEDURE
Thanks Tom. I use the ADSMGMT program that Roger created. It's just a bit cumbersome to use for the average user. All I was trying to do was show the user who was trying to access the record the name of the user or pc that had it locked. Perhaps I'll just give them the Ads Mgmt console. I took the '...
- Tue Jul 01, 2025 1:35 pm
- Forum: Xbase++ 2.0
- Topic: ADS sp_mgGetLockOwner PROCEDURE
- Replies: 2
- Views: 428
ADS sp_mgGetLockOwner PROCEDURE
Hi; Occasionally I get a call from a user that says they can't open a record because it is locked. I know ADS and xBase++ have a few functions in ADSMGMT programs that the user can trace the owner and they work fine. I was just wondering if anyone skipped all the browsers et al and just called the s...
- Sat Jun 21, 2025 4:18 am
- Forum: Xbase++ 2.0
- Topic: Ads error 5381
- Replies: 3
- Views: 4249
Re: Ads error 5381
After many hours of diagnosis this turned out to be a DHCP issue involving the 2 Domain Controllers at this site. Very strange indeed. An older Win 2008 Server was there as a backup but was the main Domain Controller and all of a sudden became unstable. Why it only affected 4 PC's out of 24 I do not...
- Tue Jun 17, 2025 5:38 am
- Forum: Xbase++ 2.0
- Topic: Ads error 5381
- Replies: 3
- Views: 4249
Re: Ads error 5381
Thanks for the input but that doesn't appear to be the issue. This client put in a Ubiquity network system that replaced the existing firewall and router configuration that worked fine for many years. I would think that if the vast majority of users can get in and process under ADs then it is probab...
- Mon Jun 16, 2025 1:32 pm
- Forum: Xbase++ 2.0
- Topic: Ads error 5381
- Replies: 3
- Views: 4249
Ads error 5381
I have a client with a Windows 2018 Server running Ads 12. He has a 25 user Ads license. About 18 of his PC's run just fine with my app which runs on the C: drive in a folder that contains the .exe files and all the xBase and express and xB2net DLLS. I have verified that they are all there. Now, 4 o...
- Thu Dec 12, 2024 12:51 pm
- Forum: Xbase++ Support
- Topic: ADS 12 and Windows Server 202X
- Replies: 2
- Views: 23328
Re: ADS 12 and Windows Server 202X
Great news. Thanks
Bob Volz
Bob Volz
- Thu Dec 12, 2024 12:39 pm
- Forum: Xbase++ 2.0
- Topic: ADS 12 and Windows Server 202X
- Replies: 1
- Views: 12886
ADS 12 and Windows Server 202X
Has anyone had any issues with ADS Version 12 on later versions of Windows Server like 2023 or 2024
My client has to upgrade his hardware from Win 2016 to the latest version and I want to make sure it will work
Thanks
Bob Volz
My client has to upgrade his hardware from Win 2016 to the latest version and I want to make sure it will work
Thanks
Bob Volz
- Thu Dec 12, 2024 8:20 am
- Forum: Xbase++ Support
- Topic: ADS 12 and Windows Server 202X
- Replies: 2
- Views: 23328
ADS 12 and Windows Server 202X
Hi;
My customer is currently using ADS 12 on a Win 2016 Server.
He has to upgrade his hardware. He is looking at WIN server 2023 or the latest Version
Has anyone had any issues with ADS 12 and the latest Windows server OS.
Bob Volz
My customer is currently using ADS 12 on a Win 2016 Server.
He has to upgrade his hardware. He is looking at WIN server 2023 or the latest Version
Has anyone had any issues with ADS 12 and the latest Windows server OS.
Bob Volz
- Sun Mar 24, 2024 6:47 am
- Forum: eXpress++ Support
- Topic: Errors
- Replies: 1
- Views: 10287
Re: Errors
Most likely Virus related. I had similar issue a few years back and it was Kaspersky denying access to certain file writing tasks. You need to add the file directory
to the 'exclusions' list .
Bob Volz
to the 'exclusions' list .
Bob Volz
- Tue Jan 09, 2024 9:19 am
- Forum: eXpress++ Support
- Topic: DCPRINT to excel
- Replies: 4
- Views: 15633
Re: DCPRINT to excel
Hi :
I finally gave up and yanked the machine. I put in a new one and it works fine. I believe ultimately that the PC had some kind of disk or registry corruption.
I tried to access "MY PC" and that wouldn't even open so I believe that confirms my suspicion.
Thanks for the advice.
Bob Volz
I finally gave up and yanked the machine. I put in a new one and it works fine. I believe ultimately that the PC had some kind of disk or registry corruption.
I tried to access "MY PC" and that wouldn't even open so I believe that confirms my suspicion.
Thanks for the advice.
Bob Volz