需要帮助开发数据转换程序 [英] Need help developing data conversion program

查看:52
本文介绍了需要帮助开发数据转换程序的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

你好。


我有VS 2008 Pro。 
我使用VB.NET,ASP.NET和AJAX开发了一些网站。 
我还开发了一些Windows程序。


我不认为自己在OOP,VB或任何其他编程技术方面精通或经验丰富。


我想开发一个程序将.MDB文件转换为SQL。


我希望它是一个Web应用程序,但如果建议将其作为Windows程序,我不介意这样做。


I想要在课堂上使用OOP。


我希望它是一个3层架构(演示,数据,业务逻辑)


< span style ="line-height:115%;字体家庭:" Arial字体","无衬线英寸;颜色:#0070c0; font-size:12pt">我希望它将任何MDB文件转换为SQL文件


我认为如果我正确设计程序,程序转换逻辑可能非常小。 
程序的大部分将在输入和输出数据的定义。


我正在寻找有关如何逐步开发此程序的指导。


我对这个程序的想法是转换逻辑永远不会改变。 
使用某种主循环,程序’ s内部表将确定要转换的MDB文件,MDB
  表的名称是什么,MDB表中字段的定义是什么以及其他相关的有关表格的信息。 
程序将始终以相同的方式工作。  只有程序数据才能确定要处理多少和哪些MDB文件。


所有SQL输出都与MDB输入相同,但输出文件现在可以在SQL 2008中打开。


我是一位老COBOL程序员,我总是使用输入,处理,输出理念开发COBOL程序,首先设计输出
  我应该从这个项目开始吗?


感谢任何帮助。


谢谢,

Tony


停止世界,我想下车!

解决方案

这只是为了好玩吗?因为Access已经有了升级到SQL Server数据库的选项。


就方法而言,如果你想使用OOP,首先要在每个层中定义适当的对象(表示,数据,业务逻辑)。


在表示层中,你可能只是有一个类,它将是用户选择要转换的数据库的表单。


在业务逻辑层中,您可能有一个Conversion类,其中包含执行任何必要转换的属性和方法。


在数据层中,您可能只需要一个数据访问类来检索数据。


如果您有分层应用示例感兴趣:


http://www.insteptech.com/techLibrary/sample code.htm


(选择名为"业务对象示例"的那个)


希望这有帮助。


Hello.

I have VS 2008 Pro.  I have developed some web sites using VB.NET, ASP.NET and AJAX.  I have also developed some Windows programs.

I don’t consider myself proficient or experienced at OOP, VB or any other programming technology.

I want to develop a program to convert .MDB files to SQL.

I would like it to be a web application, but if the recommendation is to make it a Windows program, I don't mind doing that.

I want to use OOP with classes.

I want it to be a 3-tier architecture (Presentation, Data, Business logic)

I want it to convert any MDB file to an SQL file

I feel that the program conversion logic can be very small if I design the program right.  The bulk of the program will be in the definition of the input and output data.

I'm looking for guidance on how to develop this program step by step.

My idea about this program is that the conversion logic will never change.  Using some kind of a major loop, the program’s internal tables will determine which MDB files to convert, what the names of the MDB  tables are, what the definition of the fields in the MDB tables are and other related information about the tables.  The program will always work the same way.  Only the program data will determine how many and which MDB files to work on.

All of the SQL output will be the same as the MDB input except the output files will now be able to open in SQL 2008.

I’m an old COBOL programmer and I’ve always developed COBOL programs using the Input, Process, Output philosophy designing the output first.  Should I start out that way with this project?

Any help would be gratefully appreciated.

Thanks,
Tony


Stop The World, I want To Get Off!

解决方案

Is this just for fun? Because Access already has an option for upsizing to a SQL Server database.

In terms of an approach, if you want to use OOP the first thing would be to define the appropriate objects in each of your layers (presentation, data, business logic).

In the presentation layer, you may only have one class and it would be the form for the user to pick the database to convert.

In the business logic layer you might have a Conversion class with properties and methods that perform any necessary conversion.

In the data layer you may want just a data access class for retrieving the data.

I have a layered application example here if you are interested:

http://www.insteptech.com/techLibrary/samplecode.htm

(select the one entitled "business object example")

Hope this helps.


这篇关于需要帮助开发数据转换程序的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆