 |
BorlandTalk.com Borland discussion newsgroups
|
| View previous topic :: View next topic |
| Author |
Message |
Bill Guest
|
Posted: Thu Oct 26, 2006 10:45 pm Post subject: Reinstall Microsoft Jet 4.0 |
|
|
Is there a way to reinstall Microsoft Jet 4.0? It appears that it is
not working properly as mdb memo fields are being exported as binary
rather than memo so when i export i get a message saying the field "" is
not large enough. If I try to use the Jet installer it says Jet is
up-to-date and will not let me reinstall.
Regards,
Bill |
|
| Back to top |
|
 |
C P Guest
|
Posted: Thu Oct 26, 2006 11:10 pm Post subject: Re: Reinstall Microsoft Jet 4.0 |
|
|
What code are you using? Are you still trying to go from one Access file to
another? Can you post the code that is failing? |
|
| Back to top |
|
 |
Bill Guest
|
Posted: Thu Oct 26, 2006 11:16 pm Post subject: Re: Reinstall Microsoft Jet 4.0 |
|
|
Hi CP,
I gave up on trying to "raw" export because I am a novice db developer
so I bought SMExport and Import from Salabium.
The component fails when exporting to Access... but if I Export to a
Paradox file rather than an access file the export is successful. The
developer at Salabium thinks my copy of Jet is messed up, because the
program runs just fine on his pc so he thinks if I reinstall Jet the
problem will be solved.
Should I just deinstall OfficeXP and reinstall it to get the Jet drivers
reinstalled?
Is there anyway to remove Jet and install the latest?
Regards,
Bill
| Quote: | What code are you using? Are you still trying to go from one Access file to
another? Can you post the code that is failing? |
|
|
| Back to top |
|
 |
C P Guest
|
Posted: Thu Oct 26, 2006 11:39 pm Post subject: Re: Reinstall Microsoft Jet 4.0 |
|
|
I don't think there's any uninstall for Jet. I expect if you uninstall
office, it will leave Jet installed. I think if you need to repair Jet, you
need to do it somewhat manually, and MS will have knowledge base articles
about this. Having said that, I would guess that the issue is probably Jet
settings and/or connection string settings rather than Jet being corrupted.
I don't know all the settings that well, but I know there's a whole bunch of
settings you can use for an OLEDB connection string (I expect that's the
type of connection string you're using). I'd have a look at the Jet
documentation, and the OLEDB connection string options for Access first.
Just googling, I also found this:
http://forums.overclockers.co.nz/showthread.php?p=287604
It mentions having problems dealing with Access memo fields unless you
update them in a particular order. Is it possible that something like this
is your issue, and the reason the component vendor doesn't have the same
issue is his table structure/query is different than yours and thus able to
avoid the problem? Looking at your table structure from the BDE newsgroup,
maybe it would work if you modified your table structure to be:
Method: String 255
Description: String 255
Category:: String 255
Comment: String 255
Author: String 255
Code: Memo
I put the Memo field as the last field in the table. Also I think I
mentioned before that you didn't have an obvious primary key field for your
table. Making sure your table has a primary key field may also help solve
the problem. Aside from giving Access better performance, a lack of a
Primary Key seems to cause issues in a number of database formats. |
|
| Back to top |
|
 |
Bill Guest
|
Posted: Fri Oct 27, 2006 12:16 am Post subject: Re: Reinstall Microsoft Jet 4.0 |
|
|
Thanks for your speedy reply C P,
| Quote: | I would guess that the issue is probably Jet
settings and/or connection string settings rather than Jet being corrupted.
|
I emailed the source code and the database demo application to Salabium.
He recompiled it without changing anything and the export worked on his pc.
I connect the database as follows:
procedure TfrmMain.FormCreate(Sender: TObject);
var
ADOConnSource: widestring;
DBPath: string;
ExportDBPath: string;
begin
DBPath := ExtractFilePath( Application.ExeName ) + 'code.mdb';
ExportDBPath := ExtractFilePath( Application.ExeName ) + 'export.mdb';
ADOConnSource := 'Provider=Microsoft.Jet.OLEDB.4.0;' +
'User ID=Admin;Data Source=' +
DBPath +
';Mode=Share Deny None;' +
'Persist Security Info=False;';
ADOTable1.ConnectionString := ADOConnSource;
ADOTable1.Active := True;
StatusBar1.Panels[0].Text := MinimizeName( DBPath, Canvas, 250 );
StatusBar1.Panels[1].Text := MinimizeName( ExportDBPath, Canvas, 250 );
end;
| Quote: | update them in a particular order. Is it possible that something like this
is your issue, and the reason the component vendor doesn't have the same
issue is his table structure/query is different than yours and thus able to
avoid the problem?
|
No, he has same source code and same database.
Looking at your table structure from the BDE newsgroup,
| Quote: | maybe it would work if you modified your table structure to be:
Method: String 255
Description: String 255
Category:: String 255
Comment: String 255
Author: String 255
Code: Memo
I put the Memo field as the last field in the table. Also I think I
mentioned before that you didn't have an obvious primary key field for your
table. Making sure your table has a primary key field may also help solve
the problem. Aside from giving Access better performance, a lack of a
Primary Key seems to cause issues in a number of database formats.
|
I did have it setup with an autonumber field as the first field set as
primary key. I have since changed it by removing the autonumber field
and had:
Method: String
Code: Memo
Description: String
Category:: String
Comment: String
Author: String
I switched it to your suggestion.
I tried setting the Method as the primary key in Access but it will not
permit saving the structure unless Method is not the primary key. This
is such a simple database the only other alternative i can see is to add
a autonumber field has the first field with it having a primary key.
Thanks for your help.
Bill |
|
| Back to top |
|
 |
Guillem Guest
|
Posted: Fri Oct 27, 2006 8:11 am Post subject: Re: Reinstall Microsoft Jet 4.0 |
|
|
C P wrote:
| Quote: | I don't think there's any uninstall for Jet. I expect if you
uninstall office, it will leave Jet installed.
|
AFAIK you're right. There is no uninstaller for JET 4.0.
| Quote: | I think if you need
to repair Jet, you need to do it somewhat manually, and MS will have
knowledge base articles about this.
|
If you don't have the latest JET 4.0 patch installed I would first try
to do that.
http://msdn.microsoft.com/data/ref/mdac/downloads/
You also could try to manually uninstall it. I have *no* idea if that
could help or how could it be done, though.
Good luck
--
Best regards :)
Guillem Vicens Meier
Dep. Informatica Green Service S.A.
www.clubgreenoasis.com
--
Contribute to the Indy Docs project: http://docs.indyproject.org
--
In order to contact me remove the -nospam |
|
| Back to top |
|
 |
|
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
|