Hi Teri

"Teri Welch" <trwlch@yahoo.com> wrote in message
news:s1hyd.8482$jn.4225@lakeread06...
> Thanks for the replies from everyone.
>
> 1. How can we convert MS-Access import specs to SQL Server. We import many
> data files from outside sources -- in both ASCII and Excel formats -- and
> make heavy use of import specs within VB6 programs by invoking the
> TransferText and TransferSpreadsheet functions.

You can use DTS to import from many different locations.
>
> 2. Regarding reports, must we leave them in Access? We are inclined to
> remove Access completely from the picture. Maybe that is too drastic and
> you
> would advocate otherwise. But we question the performance of using Access
> reports and the necessity to have Access open everytime a report is
> invoked
> from within VB6. Plus, we have to keep Access installed. How can we create
> the reports natively within SQL Server.

Reporting services is provided with SQL server, but this is probably not the
type of reporting you require. There may be some third party VB/ActiveX
component that will do a similar job as your current requirements.

>
> Thanks,
> Teri Welch
>

John

>
> "Ryan" <ryanofford@hotmail.com> wrote in message
> news:1103273150.975672.240020@z14g2000cwz.googlegr oups.com...
>> There are a number of tools you can use to upsize the database, but in
>> my experience, I would tend to do this manually to ensure everything in
>> the structure is correct.
>>
>> Your main issue will be with the queries as the syntax can be slightly
>> different to SQL. It's only subtle, but you would need to address this.
>>
>> Personally, I would manually create the tables (inc indexes etc...)
>> then move the data using the import wizard and do any manipulation you
>> need to get this correctly into the tables. Then, I'd address each
>> query step by step in VB.
>>
>> There shouldn't be too many issues (as a general statement). It may be
>> worthwhile looking at using views and stored procedures as these may
>> give you additional benefits.
>>
>> What you will find is that once done, it's probably quicker and much
>> less likely to have issues with record locking as SQL handles this much
>> better.
>>
>> With your reports, I would imagine you will leave these in Access, set
>> up an ODBC link to your SQL tables in access and call the reports
>> through VB as you will currently do. All you need to do is swap the
>> links over and it should be straight forward. You may do this and then
>> think about leaving the links in for the queries, but I would advise
>> not to on experience and for simplicity.
>>
>> I'm sure if there are any specific problems, a number of people on this
>> NG will help, if not, try...
>>
>>
> http://groups.google.com/groups?hl=e...ases.ms-access
>>
>> Ryan
>>
>>
>> Teri Welch wrote:
>> > Hello,
>> >
>> > We maintain a VB6 front-end application using an Access 2000
>> database. All
>> > code and forms are in VB6. The program also uses several
>> queries/reports
>> > defined in Access. For corporate reasons we must move to SQL Server
>> right
>> > away. Based on our configuration, we're hoping someone can give us a
>> feel
>> > for what's involved here. Since we're only using Access for the data
>> we're
>> > not sure what an "upsizing" would entail. Can someone point us in the
>> right
>> > direction, tell us the main gotchas, etc. Thanks a lot.
>> >
>> > Teri Welch
>>
>
>