Error when posting a compiled front End to a server

[johnham40]

I have compiled a split database and posted the back end to the server. I also posted the front end to enable the user to download to their machine

However when the user tries to open their copy, they see error codes, that I don't see. I open the same on my machine and don't get these errors.

I compiled and published the front end with no errors.

Has anyone experienced this, can someone help me out?

Thanks in advance

[hapm]

First of all please provide the exact errors, else this will end in a guessing round. Here are the first guesses:
1. Back end is an SQL server: are the odbc connections setup correctly?
2. Back end is an access database: check the paths to the back end to be the same on your productive machines and your developer machines. Or relink the tables.

[Missinglinq]

As hapm said, without details as to the exact errors, we're just guessing, here, but when apps run fine on one machine and not on another, or run fine in one version and not when run under a newer version, one the first things you have to think about are missing references. References you have loaded on the development machine may not be loaded on your users' machines.

If you haven't checked for this kind of thing before, here are Doug Steele's detailed instructions on how to troubleshoot the problem:

Access Reference Problems

Linq ;0)>

[johnham40]

I am sorry I will try to put some meat on the bones. I tried to open the db and this error appeared
"Function is not available in expressions in query expression "IIf([ID]=75, "Admin",IIf([log]>0, Left([Email],[log],"")". As I said it works fine on my machine, even when I use the posted version on the network, this error does not appear. When I access the file from a different PC, this error appears.

[Missinglinq]

If a 'function is not available,' it sounds as if the problem is what I suggested, that the errant machines have one or more missing reference libraries.

Linq ;0)>

[johnham40]

If a 'function is not available,' it sounds as if the problem is what I suggested, that the errant machines have one or more missing reference libraries.

Linq ;0)>

Thanks guys there was a missing reference

[Missinglinq]

Glad we could help!

Good luck with your project!

Linq ;0)>