VB6 Windows OS to Windows Server 2019

Hi all.

Need some help please. I'm running an old vb6 front end - access mdb back end and it's been on a local device that a few guys have logged on to over the years over our local network.

Due to covid, I purchased a server with MS Server 2019 installed and my plan is to move the application over to it and RD from anywhere however I'm struggling.

I've gone to install the application but it is trying to find the mdb from wherever the front end location is. Even when I open the front end in the same location as the mdb, it still can't connect.

The system is built in dao and I'm wary that I need to re-code to ado (if someone can confirm). Any ideas please on what I need to do to successfully install on the server? I think I may need to regsvr the dao files too?

Any help owuld be much appreciated. Can copy and paste snippets of code too.

Regards

Quote:

---

Originally Posted by jeffy10

it still can't connect.

---

Posting the error number and description might help.

Never buy a server with MS Server 2019 due to covid, it won't help. Use a mask instead and just go to bed.

Ofcourse you do have to have DAO DLL's installed on the client you're running the application on. If it automatically looks in the folder of where the front end is, then it should run.
But as Eduardo- says, without actually knowing the error you get, it's hard to tell what the problem might be. It might be something simple, as DAO, once you've got the runtimes installed (it might even come preinstalled on server 2019), shouldn't be a problem.

Quote:

---

Originally Posted by SuperDre

Ofcourse you do have to have DAO DLL's installed on the client you're running the application on. If it automatically looks in the folder of where the front end is, then it should run.
But as Eduardo- says, without actually knowing the error you get, it's hard to tell what the problem might be. It might be something simple, as DAO, once you've got the runtimes installed (it might even come preinstalled on server 2019), shouldn't be a problem.

---

He "RD"'s to the Server --> Remote Desktop
That vb6-FrontEnd is executed on the Server

And the Problem-Description sounds like hardcoded paths in the code (e.g. "c:\Program Files" vs c:\Program Files (x86)").
Nevermind that a "writable" File (and an Access-Database is a writable File) should never be placed in Program Files

Quote:

---

Originally Posted by Eduardo-

Posting the error number and description might help.

---

Attachment 185126

Hi. Thanks for replying and sorry for the delay. I’ve attached a pic to look at. The first part of the connection string isn’t coded into the program so I’m not sure why it’s there (the C\users\administrator\desktop part).

As an FYI, I haven’t installed VB6 yet to the server. Do I need to? Or do I need to register the dll files? Apologies, I’ve never used vb6 and access on a server before.

Finally, this front end will be on numerous logins with licensed user CALs, the database will be local to the server. Is that ok?

64-Bit drivers vs. 32-Bit-Drivers?
And i've seen mention of mismatches/hardcoded paths in linked-through databases

The root folder Users is a new 'facility' in Windoze

Does the old PC have a Users folder ?

Access Database Keeps Getting Corrupted
https://transferemails.com/access-da...ing-corrupted/

Quote:

---

Originally Posted by jg.sa

The root folder Users is a new 'facility' in Windoze

Does the old PC have a Users folder ?

---

IIRC it was there in Windows 7,hardly a new thing.

G'Day PD

Thanks for your insight, so helpful :)

Quote:

---

Originally Posted by PlausiblyDamp

IIRC it was there in Windows 7,hardly a new thing.

---

I'm trying to help OP 'think' about the root cause !!!