Solved

Access 2.0 ADT Problem.

Posted on 1998-01-16
4
259 Views
Last Modified: 2008-02-01
I have Access 2.0 & The Developers Toolkit.  When I try to make the distrubution disks I have no problems.  But when I try to install it from the disks I get at the end.  Didin't install completly.  Missing files.  Someone told me its to do with the INI file I attache dwith it.  But I have no clue on what to edit in the INI file.
0
Comment
Question by:ewalsh
  • 2
  • 2
4 Comments
 
LVL 5

Accepted Solution

by:
cekman earned 80 total points
ID: 1965808
Did you create a custom INI file? Are you using the runtime version with setup? Following is a copy of one of my custom ini files. You should only have to change the lines pointig to specific drive areas, and the title bar - but look close just in case.

[Options]
SystemDB=g:\scrpr\system.mda
UtilityDB=C:\MSOFFICE\ACCESS\utility.mda
AllowCustomControls=1
AllowOLE1LinkFormat=0

[Clipboard Formats]
Microsoft Excel (*.xls)=soa200.dll,1,xls
Rich Text Format (*.rtf)=soa200.dll,2,rtf
MS-DOS Text (*.txt)=soa200.dll,3,txt

[Report Formats]
Microsoft Excel (*.xls)=xls,SOA_RptToBIFF,Biff3,Microsoft Excel (*.xls)
Rich Text Format (*.rtf)=rtf,SOA_RptToRTF,Rich Text Format,Rich Text Format (*.rtf)
MS-DOS Text (*.txt)=txt,SOA_RptToAscii,1,MS-DOS Text (*.txt)

[Microsoft Access]
Filter=Microsoft Access (*.mdb)|*.mdb|All Files (*.*)|*.*|
Extension=mdb
OneTablePerFile=No
IndexDialog=No
Maximized=1
CreateDbOnExport=No
Tutorial=0

[Delimited Text]
Filter=Delimited Text (*.txt)|*.txt|All Files (*.*)|*.*|
Extension=txt
OneTablePerFile=Yes
IndexDialog=No
CreateDbOnExport=No

[Fixed Width Text]
Filter=Fixed Width Text (*.txt)|*.txt|All Files (*.*)|*.*|
Extension=txt
OneTablePerFile=Yes
IndexDialog=No
CreateDbOnExport=No

[Word for Windows Merge]
Filter=Text (*.txt)|*.txt|All Files (*.*)|*.*|
Extension=txt
OneTablePerFile=Yes
IndexDialog=No
CreateDbOnExport=No


[Menu Add-Ins]
&Add-in Manager==Wm_Entry()
&Database Documentor==Doc_PrintDataBase()
A&ttachment Manager==Am_Entry()
Im&port Database...==Doc_ImportDatabase()
&Menu Builder==CustomMenuBuilder()


[ISAM]
PageTimeout=5
LockedPageTimeout=5
CursorTimeout=10
LockRetry=20
CommitLockRetry=20
MaxBufferSize=512
ReadAheadPages=16
IdleFrequency=10


[ODBC]
QueryTimeout=60
LoginTimeout=20

[Documentor]
Option00=512
PropertyCategories=15
Option02=128
Option03=391
Option04=259
Option05=385
Option09=3

[OLE CONTROL WIZARDS]
OutlineWizardEntry=Outl1016Ctrl.COutlCtrl, Data Outline Control Wizard, wz_OutlStartup,w

[run-time options]
titlebar=SCR/PR Database
0
 

Author Comment

by:ewalsh
ID: 1965809
I'm not using a custom ini file.  Using Access's. Plus I am using the Run time.  The systems that this will be installed on do not have Access on them.  This will be a multi-user application.  I need to load it on the Network & have the users run & share the same database.
0
 
LVL 5

Expert Comment

by:cekman
ID: 1965810
That's probably your problem - look at page 10 of the book Access developers toolkit Advanced tools for custom applications. This explains that you must use a custom ini file and edit the libraries section if you're using runtime - you can't distribute the wizards with runtime.

If you don't have the book - send a comment and I'll try to type in some of the text for you. But you'll really need the book.
0
 

Author Comment

by:ewalsh
ID: 1965811
Plus I just found out.  You can't create disks while using ADT for Access 2.0 in Windows 95 if the project is going to be installed on Win 3.1 computers.  Something about some files get copied into it from the Windows directory. Below is the full text of the info i found.  Written by: Chris P. Vesper.
.......
" There are a few points to watch out for when creating install diskettes for an Access application using the Application
Developers Toolkit. The toolkit creates a professional set of setup diskettes, complete with a setup program customized with
the name of your application.

However, since the setup program copies DLL's from your system to make the install disks, you have to make sure that the
version of Windows you are running when you create the install disks is not newer than the version they will be installed on.

For example, don't create diskettes using Windows 95 to be run on a computer using Windows 3.1. This is exactly what
happened to us. We created the disks in Access 2.0, running in Windows 95. We gave then to the client, who tried to install
them in a computer running Windows 3.1. The setup program told them that it was completed unsuccessfully, and even worse,
their copy of Word 6.0 stopped working! After re-installing Word, and then creating the disks using Access 2.0 under
Windows 3.1, the install went fine."
..........

Something very important to know, since I use Win95 & the computers I'm developing for use Win 3.11!!!!!!

0

Featured Post

Comprehensive Backup Solutions for Microsoft

Acronis protects the complete Microsoft technology stack: Windows Server, Windows PC, laptop and Surface data; Microsoft business applications; Microsoft Hyper-V; Azure VMs; Microsoft Windows Server 2016; Microsoft Exchange 2016 and SQL Server 2016.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

This article is a continuation or rather an extension from Cascading Combos (http://www.experts-exchange.com/A_5949.html) and builds on examples developed in detail there. It should be understandable alone, but I recommend reading the previous artic…
Introduction The Visual Basic for Applications (VBA) language is at the heart of every application that you write. It is your key to taking Access beyond the world of wizards into a world where anything is possible. This article introduces you to…
Show developers how to use a criteria form to limit the data that appears on an Access report. It is a common requirement that users can specify the criteria for a report at runtime. The easiest way to accomplish this is using a criteria form that a…
With Microsoft Access, learn how to start a database in different ways and produce different start-up actions allowing you to use a single database to perform multiple tasks. Specify a start-up form through options: Specify an Autoexec macro: Us…

816 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

13 Experts available now in Live!

Get 1:1 Help Now