On Fri, Aug 19, 2011 at 9:37 AM, lahmbi5678 <wineforum-user@xxxxxxxxxx> wrote: > You don't have to defend yourself, wine is still a kind of challenge, it is far from being perfect, it can be very complicated and > frustrating, and the more information you give, the better. > > You should install wine 1.3.26, 1.2.3 is stable, but really old. You should start in a new WINEPREFIX and install the needed > winetricks and your application again, the simplest way is to move/rename your old .wine folder, a new .wine folder will > automatically be created by wine. > If alsan wants to keep the old Wine prefix for some reason: [code] cd $HOME mv .wine{,.backup} [/code] > There was another thread with jet40 troubles: > http://forum.winehq.org/viewtopic.php?t=12555&highlight=dao360 > Though that might be not really helpful. > > winetricks mdac and jet40 should work, if they still fail with an up2date wine, you might report a bug at > http://code.google.com/p/winetricks/issues/list > > >> >> >> > >> > Are you using Windows Mono or .NET? >> > >> >> Windows > > That question was maybe a bit misleading, I wanted to know, if you used winetricks mono to install the Windows version of > Mono (.NET substitute). > There are issues with using Mono vice using .NET, especially with SQL connections. I would recommend the following: Create a new Wine Prefix Install .NET 2.0 using winetricks Install .NET 3.0 using winetricks Install mdac2.8 and jet4.0 using winetricks Install program... alsan may also need to install the ability to configure DSN connections. That is discussed in another forum thread. James